App Performance

[SpiderBear6]

Recently I distributed a VB.Net written app to my clients. The app consisted of the main executable and 2 support dlls (all written in VB.Net) Some clients have been complaining that the app always loads slowly the first time they use it after turning on their machine. If they shut down the app and start it again, it's fast. But if they restart their machine, the app starts up slowly the first time. I thought that once the framework compiled the code into native code, it would not do it again unless something on the machine changed? In other words, I thought that the app would be slow to load the very first time it was launched, but not the first time it was launched since the machine was restarted.

Has anyone else had any similar experiences?

Thanks.

 

[Kris11]

Hi,

It could also depend on what OS your client is using. We had similar situation where if the client was using Win98, AND the OS was loading the framework to the memory only when they launch the app the very first time after rebooting the PC. Don't know if this is the same issue in your case.

-Kris

 

[SpiderBear6]

My clients are using XP. How did you fix your problem?

 

[Kris11]

No we haven't fixed this, still we are struggling with this issue.

-Kris

 

[SpiderBear6]

Interesting... what version of the framework are you using? I am using 1.1.

 

[Kris11]

We are also using 1.1. If we come across any helpful hints I will post it here.

-Kris

 

[Aboo1]

Just another poster agreeing here.
I have a large client/server app which does the exact same thing. We use Windows 2000 and Windows XP. Framework version 1.1

Loads dog slow the first time, then speedy after that. Every time the user reboots, they go through the dog slow process again. Frustrating!

 

[SpiderBear6]

It's like it's not saving the compiled version or something. Sounds like a bug.

Yes frustrating indeed.

 

[SpiderBear6]

P.S. Funny... the whole idea of the framework and the JIT compile was to improve performance.

 

[phunugus]

i hate this, i betcha the java framework doesn't do this

 

[chiph]

P.S. Funny... the whole idea of the framework and the JIT compile was to improve performance.
It does ... just not the first time it gets called.

You can look at running NGEN to skip the JIT, but remember that NGEN would need to be re-run after the user changes their Windows configuration (installs service pack, etc).

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first

 

[SpiderBear6]

"It does ... just not the first time it gets called."
Yeah... every time you boot the machine.

Yeah, I know about ngen, but I doubt my users are going to remember to run ngen when they do something to their machine. There has to be a better way.

 

[chiph]

Put the NGen commands in a batch file that's in their startup group.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first

 

[SpiderBear6]

Sounds like an interesting idea. So everytime they start their machine, it runs NGen? How long does it take to run ngen?

 

[chiph]

Depends on how many assemblies you have, and how complex they are -- too complex for me to give a simple answer.

You'd have to try it and see how well it performs.

Chip H.


If you want to get the best response to a question, please check out FAQ222-2244 first