Bringing up a Linux guest is a resource intensive process: Linux touches every page of it’s memory allocation and does a lot of fairly dumb things trying to figure out it’s environment. If you have a lot of guests all trying to come up at once, you will likely overtax the capability of CP to service all those demands unless you are grossly overconfigured in CPU and memory. Pausing a few seconds between bursts of guest startup activity lets CP get it’s house back in order before the next onslaught begins.
Hardcoding 15 seconds is not a great idea — the right way to to do this is to wait for a positive acknowledgement from each server that it has started completely — but it’s not a bad SWAG to wait. The SYSVINIT code we wrote for CMS does the positive ack processing; you might want to look at it in place of timing based approaches like the one below. -- db On 11/4/09 12:48 PM, "sunny...@wcb.ab.ca" <sunny...@wcb.ab.ca> wrote: What is the reasonable setting for sleep time after issue xautolog server? On the planning and Administration "Steps for automatically starting linux virtual servers and other virtal machines" say: 1. After every third XAUTOLOG statement that starts a Linux virtual server, add this statement: CP sleep 15 sec Can someone tell me why? Sunny Hu ________________________________ This message is intended only for the addressee. It may contain privileged or confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original email. Thank you. (Sent by Webgate1)
