Date:  Wed, 21 May 2008 23:11:08 +0200
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:13025] Re: WMware VI3 setup
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200805212311.08957.bq (at mark) solarspeed.net>
In-Reply-To:  <479e01c8bb74$0c6c3e40$967da8c0@thomasferrari>
References:  <4831D9E5.4020803 (at mark) virtbiz.com> <200805211906.57183.bq (at mark) solarspeed.net> <479e01c8bb74$0c6c3e40$967da8c0 (at mark) thomasferrari>
X-Mail-Count: 13025

Hi Thomas,

> We are running some of our BQ machines as VM's on Virtual Infrastructure 3
> from vmware, and are watching CPU go up every day at 4AM - that$Bc`QT(B where
> daily 4:02, weekly 4:22 and monthly 4:42 crons start.
>
> So, how much can we move these jobs around, without interfering too much
> with the system.
>
> Anybody got any experience running these jobs inside this interval
> 0:02, 0:22, 0:42       to     6:02, 6:22, 6:42

Yes, when you run multiple virtual servers on the same box, then it's a good 
idea to spread the execution of the daily cronjobs around a bit. So that they 
don't all run at the same time. When you want them to run should be 
determined on when the most/least activity is. For instace: You'd want to run 
the logrotates at times that are usually quiet - activity wise. 

Aside from that moving the cronjobs to run at different times is technically 
no big deal.

-- 
With best regards,

Michael Stauber