R
ramadu
Hi,
I am a developer in a company which makes a large scale .net windows
application. Recently, my users have been complaining that after a
period of inactivity of about 15-20 minutes, the next action that they
perform takes 30+ seconds to execute. The same action normally would be
done in around 5 seconds.
The application consists of multiple dlls (data access layer, system
functions, UI layer etc.) and consumes on an average around 10-15 MB of
memory and peaks to about 40-50 MB during complex processing. I'll be
happy to provide more information if required.
What can I do to address this issue? Thanks in advance.
- ramadu
I am a developer in a company which makes a large scale .net windows
application. Recently, my users have been complaining that after a
period of inactivity of about 15-20 minutes, the next action that they
perform takes 30+ seconds to execute. The same action normally would be
done in around 5 seconds.
The application consists of multiple dlls (data access layer, system
functions, UI layer etc.) and consumes on an average around 10-15 MB of
memory and peaks to about 40-50 MB during complex processing. I'll be
happy to provide more information if required.
What can I do to address this issue? Thanks in advance.
- ramadu