On Mon, Apr 06, 2009 at 12:17:18AM +0000, SRabbelier@xxxxxxxxx wrote: > Heya, > > On Mon, Apr 6, 2009 at 01:38, Robin H. Johnson robbat2@xxxxxxxxxx> wrote: >> Relatedly, throwing more RAM (6GiB total, vs. the previous 2GiB) at the >> server >> in this case cut the 200 wallclock minutes before any sending too place >> down to >> 5 minutes. > I'm curious what kind of hardware changes you made to achieve such an > enormous effect? Was it just added RAM on the same machine? No, see the paragraph previous to that, showing it was a different machine that just happened to have 6GiB of RAM. The key difference is that having 6GiB of RAM was enough to stop the swap/OOM-killing of git-pack-objects/git-upload-pack that happened on the slow server, which I considered to be entirely unwarranted since the pack was already generated and perfect for use. "Slow" server: - deadline scheduler - AMD Opteron 1210, single socket, 2 cores @ 1.8GHZ - 2GB Reg ECC RAM - 2x ST3250620AS, RAID1 - 100Mbit internet feed, co-located in Texas. "Fast" server: - deadline scheduler - Intel Core2 Q6600, single socket, 4 cores @ 2.4GHz - ~5.7GiB of cheap RAM (6GiB in the box, 256 not usable due to BIOS MTRR brokeness) - 7x ST3320620AS, RAID-5. - Sitting on my home LAN, with a very crappy upload bandwidth to the Internet. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : robbat2@xxxxxxxxxx GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Attachment:
pgpmTGC4wDc2X.pgp
Description: PGP signature