Hello
We have got a .NET application (.NET 1.1) that the users start from a
network share. After start up the user logs in and he can then minimise the
application, so that it appears as an icon down on the right hand side (like
the date information, msn icon etc.). Now when the user wants use the
application he must first maximise it or relogin (if he logged out before).
On some machines this maximisation/startup time lasts extremely long (up to
60 seconds and more). What could be the reason for this?
However this peculiar behavior seems only to happen on workstations that
have been running a long time (and the application has also been started a
long time but i dont know whether this makes a difference). There seems to
be quite a lot of network activity when maximising/restarting the
application. To me it seems more or less acceptable that the client must get
the application again from the network share when it was minimised for a
long time (os frees resources). But how can it possibly take take that long
(much much longer than the normal startup time).
What might could have an influence is that the application tries to minimise
memory usage by using the corresponding windows api.
[DllImport("kernel32.dll", SetLastError=true)]
public static extern int SetProcessWorkingSetSize ( IntPtr hProcess, int
dwMinimumWorkingSetSize, int dwMaximumWorkingSetSize);
accessed like this:
//release memory for other applications
MemoryUsageMinimiser.SetProcessWorkingSetSize(Process.GetCurrentProcess().Handle,
-1, -1);
Does anybody have an idea what could be the reason for this strange
behavior. I would apprecheate any help.
Thanks in advance
Daniel.
|
Similar Threads
