To be honest i have Dell XPS M1530 - Intel Penryn T9300 - 2.5GHZ and Nvidia M8600GT. I was running Vista x86 2 years ago, then switched to Linux x86, then after a while switched to Windows 7 x86 and after that found about Windows Server 2008 R2 and switched to it, but it is x64. It was my first system x64 that i installed to my notebook. I have 2GB of RAM, and it seems enough, but i think 4GB would be better for x64 system. Also i had some BSODS, but found the reason about them. External Card Reader driver caused them

Wow you switched OSes alot.

Lal, my first computer was equiped with Windows ME So it seems Windows 2008 R2 is working well on my laptop. Watching movies, play games - no complaints about it. But theres still something, that i want to do. With firefox running(4 tabs atm) system uses 550-560MB of RAM. I want to make that number *if its possible* lower. I have tweaked services already, tweaked some processes, still cant figure out what to do next x.x

there isnt much you can do, it just plainly uses more ram.

I have converted to R2 after reading about the conversion.

I dont really care about superfetch, not missing it.

I also managed to edit imageres.dll so i dont get the blue and yellow noobie admin icon on system tasks. Happy so far!

Still have some changes i want to put in though, but im getting there.

FF has always been bloated. ever since version 2.0.x. I use IE8.

The issues with RAM is that I would rather have an application smartly using RAM and using less commit charge.

commit charge usage is more important then RAM usage becuase using excessive commit charge causes your HD to "thrash" and possibly wear it down quicker and causing servere system slowdowns. RAM can take more of the beating then your HD can.

Now the commit charge of FF with 10 tabs that I had open for a week was 6.7GB just for FF alone! the same for IE8 was 2.6GB! commit charge is what is only being used in the paging file and NOT in RAM.

my IE8 RAM usage with 15 tabs is 430MB and commit charge is 3.8GB. Not bad for leaving this session on for more then 1 week. I always go into task manager and kill a process taking up more then 320MB in my commit charge for more speed.

However on windows server 2008 R1/R2 you can install a tool called Windows System Resource Manager, to automatically do this for you. I have mine setup to kill any IE8 process that uses 512MB or more commit charge, and then it will close it, the tab will recover, and no worries. This is specially good for using on youtube since 8 youtube vids will often get the commit charge that high!

I have an article on this forum somewhere describing this technique. However with FF you cannot do this as all the tabs run in a single process, whereas IE8 runs each tab in a seperate process. You might do this with chrome, however the results were'nt so good.

Firefox has kind of a bad reputation, which isn't at all deserved.

Make sure you are using the 3.5 series, get rid of any addons and keep it updated.

It will allocate some memory just as it should, but it certainly shouldnt be hogging it.

I've had my FF open for quite a few hours, and have 3 windows and maybe 60 tabs, and I'm not using more than 270mb.

What sites do you have open JF?? wow that's the smallest ram usage for FF I've seen.

I have discovered today firefox x64. Just type in google, and u will find it. Holy crap this thing runs much smoother and consumes less RAM.

does it have a 64 bit flash plugin?? adobe doesn't want anything to do with x64 systems, yet thier president spends 200K a year on 'aircraft expenditures'... adobe has always sucked. x64 bit systems have been out for a long time and yet adobe with over 10,000 employees cannot make a simple plugin that's 64 bit.

MS doesn't have MSDN for nothin' yah kno.

Please nag at adobe for not having an x64 bit version of flash plugin. we need as many as we can.

rmxcat, yeah correct! THeres no x64 adobe flash plugin, and that makes me sick