Initial opening speed

Hi

My vb.net seems to be slow on initial loading. My clients are not impressed
as they had used the ms access version of the app previously and think that
the old app is faster in loading. I understand .net apps need to compile
themselves before execution. Is there any way I can speed up this process or
in general do anything else to speed up initial loading of the vb.net app?

Thanks

Regards

Teemu
Fri Feb 22 10:48:46 CST 2008


"John" <John@nospam.infovis.co.uk> kirjoitti viestissä
news:%23jUgpQWdIHA.748@TK2MSFTNGP04.phx.gbl...
> Hi
>
> My vb.net seems to be slow on initial loading. My clients are not
> impressed as they had used the ms access version of the app previously and
> think that the old app is faster in loading. I understand .net apps need
> to compile themselves before execution. Is there any way I can speed up
> this process or in general do anything else to speed up initial loading of
> the vb.net app?

There is a utility called ngen in .NET Framework's directory. Here is more
information:
http://msdn2.microsoft.com/en-us/library/6t9t5wcf(VS.80).aspx

But unfortunately it is a fact that .NET applications start slowly at the
first time.

-Teemu

Andrew
Fri Feb 22 10:51:06 CST 2008

Hi John,

The problem is that it takes time for the .Net Framework to load all
assemblies into memory when it is loaded for the first time. That's the
cause of this delay at the initial start. I believe that you may use the
ngen utility to force the required assemblies to be loaded. Please review
the http://msdn2.microsoft.com/en-us/library/6t9t5wcf(VS.71).aspx article
in the MSDN.

Thanks,
Andrew

"John" <John@nospam.infovis.co.uk> wrote in message
news:%23jUgpQWdIHA.748@TK2MSFTNGP04.phx.gbl...
> Hi
>
> My vb.net seems to be slow on initial loading. My clients are not
> impressed as they had used the ms access version of the app previously and
> think that the old app is faster in loading. I understand .net apps need
> to compile themselves before execution. Is there any way I can speed up
> this process or in general do anything else to speed up initial loading of
> the vb.net app?
>
> Thanks
>
> Regards
>
>

kimiraikkonen
Fri Feb 22 11:09:06 CST 2008

On Feb 22, 5:04=A0pm, "John" <J...@nospam.infovis.co.uk> wrote:
> Hi
>
> My vb.net seems to be slow on initial loading. My clients are not impresse=
d
> as they had used the ms access version of the app previously and think tha=
t
> the old app is faster in loading. I understand .net apps need to compile
> themselves before execution. Is there any way I can speed up this process =
or
> in general do anything else to speed up initial loading of the vb.net app?=

>
> Thanks
>
> Regards

John,
Similar issue had been discussed here with same symptoms.
Unfortunalely, .NET is not as fast as other technologies like VC++,
MFC or VB (6) classics. I think faster memory speeds are a bit helpful
for overcoming on this issue.

http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_t=
hread/thread/e36d3712e4d30b3a/7d003acbe4a4b170?hl=3Den&lnk=3Dgst&q=3Dslow+st=
artup#7d003acbe4a4b170

Plus, there's a temporary method which can be applied. As you know, if
you run a .NET application, the second launch of that or an another
application is done much more faster (almost less than one second).
That's why you may want to write an empty .NET application and put
this into startup, it should run automatically and will provide help
to speed up other main applications's initial launch accelerations.

Cowboy
Fri Feb 22 12:50:58 CST 2008

You can ngen your assemblies, but be careful and make sure you have a
version for their machine, as ngen is a native gen utility. If these are
clients, you are best to set up ngen to run on their machine when you
install, as you will be guaranteed to have it ngened for their machine.

If you do not like this route, there are third party tools that compile .NET
assemblies into native code, which essentially makes them non-.NET programs.
This is one option you can try if all other attempts fail.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************
"John" <John@nospam.infovis.co.uk> wrote in message
news:%23jUgpQWdIHA.748@TK2MSFTNGP04.phx.gbl...
> Hi
>
> My vb.net seems to be slow on initial loading. My clients are not
> impressed as they had used the ms access version of the app previously and
> think that the old app is faster in loading. I understand .net apps need
> to compile themselves before execution. Is there any way I can speed up
> this process or in general do anything else to speed up initial loading of
> the vb.net app?
>
> Thanks
>
> Regards
>
>

John
Fri Feb 22 21:41:05 CST 2008

Thanks. Is there a way to include ngen into the setup?

Thanks again.

Regards

"Teemu" <tsirkia@hotmail.com> wrote in message
news:c2Dvj.300564$3M3.195157@reader1.news.saunalahti.fi...
>
> "John" <John@nospam.infovis.co.uk> kirjoitti viestissä
> news:%23jUgpQWdIHA.748@TK2MSFTNGP04.phx.gbl...
>> Hi
>>
>> My vb.net seems to be slow on initial loading. My clients are not
>> impressed as they had used the ms access version of the app previously
>> and think that the old app is faster in loading. I understand .net apps
>> need to compile themselves before execution. Is there any way I can speed
>> up this process or in general do anything else to speed up initial
>> loading of the vb.net app?
>
> There is a utility called ngen in .NET Framework's directory. Here is more
> information:
> http://msdn2.microsoft.com/en-us/library/6t9t5wcf(VS.80).aspx
>
> But unfortunately it is a fact that .NET applications start slowly at the
> first time.
>
> -Teemu

Teemu
Sat Feb 23 06:02:05 CST 2008


"John" <John@nospam.infovis.co.uk> kirjoitti viestissä
news:e9d2o3cdIHA.4696@TK2MSFTNGP05.phx.gbl...
> Thanks. Is there a way to include ngen into the setup?
>

You can run ngen during the setup process. Ngen is installed on every
computer with .NET Framework.

-Teemu

Rad
Thu Feb 28 15:36:57 CST 2008

On Fri, 22 Feb 2008 12:50:58 -0600, Cowboy (Gregory A. Beamer) wrote:

> You can ngen your assemblies, but be careful and make sure you have a
> version for their machine, as ngen is a native gen utility. If these are
> clients, you are best to set up ngen to run on their machine when you
> install, as you will be guaranteed to have it ngened for their machine.
>
> If you do not like this route, there are third party tools that compile .NET
> assemblies into native code, which essentially makes them non-.NET programs.
> This is one option you can try if all other attempts fail.

You could also have a look at your code and see if you can identify any
bottlenecks. Run it through a profiler like RedGate ANTS or JetBrains
DotTrace. You might be find some bottlenecks where you can improve
performance
--
http://www.thinkersroom.com/bytes