| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3152.1 | Did you do any homework already? | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Fri Dec 20 1996 18:26 | 5 |
| 3152.2 | If you already know the answer... | EPS::DEANE | | Mon Dec 23 1996 14:09 | 7 |
| 3152.3 | why don't you spend time looking instead of asking us to do the leg work for you? | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Mon Dec 23 1996 15:38 | 38 |
| 3152.4 | working set trimming | BEET::EAGAN | Among the fashion impaired... | Mon Dec 23 1996 16:27 | 23 |
| 3152.5 | decwet::windows-nt, note 5465.1 | CFSCTC::HUSTON | Steve Huston | Mon Dec 23 1996 16:59 | 4 |
| 3152.6 | | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Mon Dec 23 1996 18:33 | 32 |
| 3152.7 | | EPS::SLATER | Marc, DTN 381-2445 | Fri Dec 27 1996 17:09 | 29 |
| 3152.8 | Try SetProcessWorkingSetSize | DECWET::MVB | Monty VanderBilt | Mon Jan 27 1997 10:32 | 23 |
| Try calling SetProcessWorkingSetSize(). It's documented in MSDN. The
arglist has a process handle so you can use this on another process
given a suitably priviledged account. If you set the
MinimumWorkingSetSize to a large value you can probably get the
behaviour you want. I haven't tested this.
BOOL
WINAPI
SetProcessWorkingSetSize(
HANDLE hProcess,
DWORD dwMinimumWorkingSetSize,
DWORD dwMaximumWorkingSetSize
)
dwMinimumWorkingSetSize - Supplies the minimum working set size for the
specified process. The virtual memory manager will attempt to keep at
least this much memory resident in the process whenever the process is
active.
I also checked on the "link /ws:aggressive" flag but "aggressive" is
the only option here. I was hoping there would be "/ws:wimpy". :-).
|