I found it takes a few minutes to create pool and prepare the job, I am thinking to keep the pool to get rid of the overhead.
Thanks
Lidong
I can try and answer this but folks can correct me, AFAIK: refer to this document: https://azure.microsoft.com/en-us/pricing/details/batch/
In batch as doc states: “Virtual machines are billed per-second rounded down to the last minute.”
Most of the pricing structure is well document and seems like it’s just few cents per hour.
One general suggestion could be that once you are done with your compute you can always re-scale your pool back to 0.
You probably want to add more to your question if you are keen to discuss any specific scenario so that right folks can answer in detail.
Hope this helps, but add more most o the content above is general purpose. Thanks
Update https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
Related
I am a PO leading a small development team for enhancements to our PeopleSoft Campus Solutions application for a Medical School.
We are using the Sprint functionality in ADO to assign stories from our backlog to the Sprint, create the relevant tasks for each story (mainly development, testing, deployment) and assign the tasks to resources who, in turn, provide effort values (original estimate, remaining, completed). We also make sure our capacity is properly set, with resources OOO time and school holidays configured to get an accurate team and resource capacity. The team updates their effort numbers daily to ensure we are tracking burndown.
While we always start the Sprint with the remaining work hours under team capacity (and the same at the resource level), we have historically left alot of remaining work on the table at the end of the Sprint.
My leadership wants to answer the question "Why was the work left on the table?". Of course, there could be MANY reasons, we underestimated the effort, we were blocked on a task (for example, we can't start the testing task until the development is done), the resource didn't actually have the calculated capacity due to being pulled into other meetings or initiatives, or (and I don't think this is the case) people were just plain lazy.
What reports/analytics can I leverage to help answer this question? Even just seeing a list of remaining tasks per resource with remaining task effort and with a total amount of work remaining per resource overall would be helpful, but I can't seem to find anything.
Any suggestions or guidance is appreciated!
You can use Queries to find the remaining tasks(add column option->Remaining Work) and save the query into Shared Queries.
There is a query results widget in dashboard to display the query in Shared Queries. Do not forget to add Remaining Working in widget.
Remaining Work:
You could refer to the document: Adjust work to fit sprint capacity
I am a newbie to anylogic simulations. In my project, I want to take out queue size at every time step from a service block and create a dataset. Similarly, I also want to take out the mean queue size from the same after every replication and create a dataset of that as well. Can anyone help me with how to do it?
Welcome to SOF and AnyLogic. Best post separate issues for separate questions, see this intro to SOF for AnyLogic users.
But for now:
I want to take out queue size at every time step from a service block and create a dataset.
Use a cyclic event that calls myDataSet.add(myServiceBlock.queue.size())
I also want to take out the mean queue size from the same after every replication and create a dataset of that as well.
In your experiment, add a DataSet myMeanResults. In the "On Simulation end" code box of your experiment, call myMeanResults.add(root.myDataSet.getYMean())
Make sure your Datasets can keep enough values!
Also, always check the AnyLogic help and example models. Very often, these basics are covered there already. Else, tell us what you already tried :)
I'm pretty new to AnyLogic and I want to know how I formulate my condition in the Select Output block. Regarding my queue, I have a maximum capacity of 2, and if the queue is full, the new arriving customer has to leave, and therefore does not wait, so this would be a lost customer. Can anyone help me out here?
Thank you.
enter image description here
Simply use queue.size()<2
Please first try to work through the step-by-step tutorials as this is, indeed, very basic ;)
I am modeling ticket system with various SLA. The model must contain several service blocks with different reaction time ( from 2 to 32 hours). In the service block only working hours should be taken into account. So in the service block timeout should stop when non-workong hours and on the weekend. Could you please kindly tell me how i can realize it?
Thank you very much in advance!
I can think of two answers, one simplified but works in many cases, the other more advanced and probably more accurate:
Simplified approach: I would set the model in hours and keep everything running as is without any stop. So, at the end of the simulation, if the total time is 100 hours and you know that you have 8 hours/day with 5 days/week, then you'd know the total duration is 2.5 weeks. Of course, this might have limitations or might become more complex later on if you want day-specific actions (e.g. you want to differentiate between Monday, Tuesday, etc.)
Advanced more accurate approach: Create resources whose capacities are defined by schedule and assigned them to your services. Create a schedule and specify the working hours in that schedule. Check the below link to learn more about schedules. I call this the more advanced approach because you need to make sure the schedule is defined correctly and make sure all elements in the model are properly controlled (e.g. non-service blocks such as source, delays, etc.).
https://help.anylogic.com/topic/com.anylogic.help/html/data/schedule.html?resultof=%22%73%63%68%65%64%75%6c%65%73%22%20%22%73%63%68%65%64%75%6c%22%20
I personally would use the first approach if the model is rather simple and modeling working hours is enough for analysis. Otherwise, I'd go for option 2.
Finally, another option I'd like to highlight is the "suspend/resume" functions. I am only adding this because you asked "how to stop timeout". So these functions specifically stop and resume timeout. But you'll need to define the times at which they are executed (through an event for example).
I am discovering the Azure Delivery Plan but I don't understand why I don't see all my Features in there.
This is what I am talking about:
https://learn.microsoft.com/en-us/azure/devops/boards/plans/review-team-plans?view=azure-devops&tabs=plans-preview
I have looked at the Tags, owners, start/end dates, and so on but can not find any criteria which indicate why I see certain Features and not others.
I am also a member of the projects that I do not see.
Can anyone shed some light for me on this one?
In my test, if the dates of two iterations overlap, the features under the iteration will not be displayed.
For example:
If the date does not overlap, the features under the iteration will be displayed normally.
You can check if this is your case.
This one is actually on me and was kind of logical.
The features were on the backlog and didn't have any iteration assigned, hence, there were not showing below any iteration.
Thank you for the suggestions and feedback! Case closed!