> (Somebody want to explain what that means - Stan?) > > http://support.microsoft.com/default.aspx?scid=KB;en-us;q247904
That article explains the windows terminal services problem thoroughly. Why are we discussing a microsoft OS memory management problem on this list? Oh, maybe memory management needs some explanation: Programs are written today in portable, high level languages (C, C++). Programmers do not explicitly manage memory locations, as modern OS's handle this for them. This is because systems run many programs simultaneously (multitasking), and thus one programmer cannot take into account what other programs (and what physical memory locations they are using) may be running on the system. So programmers use virtual addresses, which the operating system memory management code translates into physical memory addresses at run time. The problem described in the article above arises because the OS comsumes memory in order to manage the virtual->physical mapping of memory locations. The consumed memory stores the translation tables, which map virtual memory addresses to physical memory addresses. Kind of a double edged sword, eh? The more memory a system has (thus allowing more processes to run, or larger processes, i.e. databases), the more of that memory is consumed just to manage memory. This is the price we pay for progress... ;) Oh, wasn't this thread about P4 Xeon performance (or lack thereof :)? Answer in next post... StanTheMan TheHardwareFreak rcon admin at: Beer for Breakfast servers <http://bfb.bogleg.org/> 209.41.98.2:27016 (CS multi-map) 209.41.98.2:27015 (DoD) 209.41.98.2:27017 (CS militia/dust2) Dallas, TX _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
