I have been watching the perf logs closely on our terminal server which regularily suffers form freezes during working hours. Here is the trend. Initially I tought it was maybe just a disk bottle neck and not memory as the "available megabytes" doesent go any lower 300 and page file usuage doesent go much of 30% during the course of a day.Here is the trend.

-Up to 8am the box sits idle, obviously
-during the course of the day the processor never goes of 28%
-as more users login the availble mega bytes of memory works it way down form 3000 to 300
-pages per second works it way from ~200 to 2500
-during the big spikes of pages the logical disk usage% sometimes hits 500 (insane)
-during the big spikes the the disk write q length will hit up to 4 and the read length is maybe half of that.

Our system has 4 gigs of ram and a 4 gig paging file

here is a link to a bmp of the perf log
http://imkaudio.com/perf.bmp

It appears to me we could benefit form both another 4 gigs of ram and setting up a stripe across 2 dedicated drives and moving the paging file to it.

Any ideas?