cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jessica Tomechak (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1918) Tuning Guide
Date Thu, 04 Apr 2013 06:39:15 GMT


Jessica Tomechak commented on CLOUDSTACK-1918:

Here are some questions from an actual user who experienced performance issues.

Need a document on how to determine settings for workers and also how to monitor threads to
improve/balance the performance.

How to maximize the number of simultaneous executable requests without impacting any other
functions? Setting the appropriate number of workers is one important factor. What else?

Having done so, then how to set up monitoring so we can be aware when the requests exceed
the maximized number? This is to avoid situations like hosts in alert state.

If the monitoring reveals requests getting too numerous, how to decrease the number of requests?
Would tuning the timeout related parameters like ping.interval and ping.timeout help? What

> Tuning Guide
> ------------
>                 Key: CLOUDSTACK-1918
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>            Reporter: Jessica Tomechak
> For admins. How to get the best performance for a variety of scenarios. Using global
settings, other tuning controls.
> With all the parameters available to cloudstack, we really could benefit documenting
them in a way that could show what performance gains could be be gained by tweaking each.
Also what params work best, or need to be modified together. (Ahmad Emneina)
> First step here would be to simply beef up the UI-displayed descriptions of the global
config parameters.
> If possible, use one source file to generate both improved UI tool-tips for the config
settings and an alphabetical reference in docs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message