Paging file

[Chris]

I have the following problem with the paging file on Win 2000 workstations
(256 MB / SP3 / Single physical disk) running our custom user interface app
(VB6) and SQL Server. During periods of user inactivity Windows pages out
memory and, when the user starts using the app again, there's a long period
of disk thrashing while memory is paged back in. Analysis has indicated
that neither our apps or SQL Server is doing anything to trigger or inhibit
the thrashing.

Alot of this problem is due to the fact that our user interface app holds
lots of data in memory. The app uses a further 50 VB6 COM DLLs.

Apart from the obvious (Reducing memory usage of our apps / Using
recommended page file size & optimising for foreground apps / Optimising SQL
Server / Disabling un-needed O/S components / Reducing disk access /
Upgarding hardware) is there anything that can be done to shorten the disk
thrashing period? Is there anything in the WinAPI to control paging for
individual apps?

 

[DL]

'maybe' increasing ram to 512mb ?
but perhaps you included that in 'obvious'