Eric Brown wrote:
Most people can probably get away with using chroots instead of
completely separate machines for testing. The only major concern
there is whether or not you have the computing resources available to
build on the same host that your production applications run on.
I interpreted corporate to mean "everyone is gone by 6pm" so it's roll
in around 11am on Tuesday and do an update starting around 6:30pm that
night. However that might not be the case. I've never had issues doing
updates in off hours usually 1-3am on lightly loaded servers, but that
depends on your hardware and workload.
Here are some compile times since I was playing with some new boxes today.
3.0Ghz Xeon w/2MB cache w/HT, 1GB RAM, single drive
time to compile Mysql 5.0.19 w/-j3 - 23 minutes
2x 3.0Ghz Xeon w/2MB cache w/HT, 4GB RAM, raid 1 w/256 cache
time to compile Mysql 5.0.19 w/-j3 - 9 minutes
2x dual core 2.8Ghz Xeon w/2MB cache/core w/HT, 8GB RAM, raid1 w/256 cache
time to compile Mysql 5.0.19 w/-j8 - 7 minutes
In the last case I could renice or use -j5 and load would stay under 3
meaning the OS could have the remaining resources which would likely be
enough in off hours. However some of these boxes may be of a slightly
different scale than other admins
I am curious about how other people do updates once they've decided
there is no issue and how hardware/load plays a part in the process.
kashani
--
[email protected] mailing list
