Originally Posted by
SilverIceForum
1) System.exe is the main Windows kernel, reason this process at times can eat up a lot of memory, it is the process that speaks both hardware language and software language to make is Joe Public speak, it is your system translator and prioritizes everything.
2) csrss.exe
Handles majority of your windows and part of the System Shell dealing with command prompts, dialog boxes, and drawing windows and such, so not surprising it eats up a lot of resources when under load being it also controls all the thread splitting management within windows as well.
3) Yes, under load when running Cabal, which when executed, Gameguard and some other processes hide the executable's threads in taskmanager to make it harder for cheat programs find and hook into the process to tweak its memory pages etc. Have to remember, while cabal is focused (to the front process window, in full screen it is the top window) will eat up a lot of processor and memory, but you also have to remember DirectX is working in the background to do all the 3d/2d drawing and sound, which again eats up a lot of resources at times. The game may seem to be lagging more at times than others on you with more memory installed, 3x the amount you had before.
512mb before, windows was using a lot of pagefile (hard drive space for virtual memory) that it continually had to work with to swap memory instructions/pages around, thus lagging your game to its slowest anyway, you didn't see or feel all the background lag. Now we step forward to 3x the memory you had, more information is up in faster reading RAM compared to slower reading hard drive space, you feel the lag spikes when the system is swapping/reading information to hard drive virtual memory or loading new data into RAM off the hard drive far more than you did with only 512mb best way I can explain it to you really. Though adequate to do the job, Microsoft's memory management is really an ugly beast and is half as capable as a Unix style memory management, keeping unnecessary old data in RAM/virtual memory when not needed, etc, you get issues like above.
I do see when I first load the game considerable hard drive read lag as a lot of secondary data is loaded into RAM from the hard drive, but this generally subsides after about 15-45 seconds depending upon how populated the map near me is when spawning into game ;-). Had an old Turion laptop with 128mb ATI Gfx chip and 1.5gig RAM, like stated above ran pretty smoothly most of the time until like in NW you had 30+ ppl all in one spot bashing the hell out of each other I'd get into trouble of serious video stepping, but bared with it none the same. 3gigs RAM, 512mb Gfx Card, dual core cpu max this game really needs to run above average to super, 1.5gigs RAM, 256mb Gfx Card, single core cpu is about an average experience ingame for anyone. Above and beyond those then you are just talking extra frames per second per dollar wasted really IMO.
Bookmarks