I guess that makes sense.. I just didn't think the PAE stuff made _that_ much of a difference.
So... if I can have my sound and eat it too, anyone know an easy method of i386->amd64 conversion of a production server running 20 or 30 live services? (; jam wrote: > On Wednesday 21 May 2008 02:47:23 [EMAIL PROTECTED] > wrote: > [snip] > >> If you have references for the 'slowness and other issues' or 'hardware >> support issues' I'd love to see them. I've not found any quantitative >> analysis of i386+PAE vs. x86_64/amd64 performance. I have to assume that >> while there is necessarily some some slowdown in rewriting memory addresses >> to access +3GB RAM, it's not so significant that it causes the measured >> load average to go up 400%. >> > [snip] > It is significant specially doing **exactly** what you are doing > > 64: a large footy field > 32: a small room with lots of drawers, You can only open 1 draw at a time: > > usual big mem scene: open a drawer and do lots of work, open another ... > > ltsp: open a drawer, do a little work, close the drawer, open another > drawer ... > > The more work you do, as opposed to doing hard work, the more you need 64. > > In your case while you are 'opening the drawer' and 'closing the drawer' the > work is piling up (Load Avg up). Open and close are non trivial so if you do > it too often ... and you have 8 CPUs all waiting in line for their own > drawer ... > > James ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
