But when the client, say opens a form that has a grid that is being loaded as this poster has shown, doesn't it have to load assemblies, do security checks and JIT? Sure, if he doesn't it the second time it will be faster, but many users will not be opening the same forms over and over again. So I don't see that as a good performace check (doing it multiple times).
-----Original Message----- From: William Oliveri [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 2:09 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Windows Application painfully sluggish On Tue, 28 May 2002 14:02:08 -0400, Marsh, Drew <[EMAIL PROTECTED]> wrote: Oh heck yeah. That's what I was doing. One click and kill the app. Then try again. Now it's much different, faster. I was worried that if this was happening on a 1.8Ghz with 512 of ram what it might do on a lesser machine. thanks. >Question: Is your test a one time only thing? By that I mean, do you just >launch the app and click the button once? If so, this is hardly a good test >as there's so much more going on than just the control loading data (i.e. >assembly loading, security checks, JIT compilation). You should at least >click the button twice. > >Later, >Drew >.NET MVP > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
