My application takes up 1.5GB of memory in release mode, but only 370mb in debug mode...why?

[John Sheppard]

Hello all,

I have an application written in VB.Net that comsumes a webservice.

We are having issues with speed. I have not ruled out a webservice problem,
and this was my first guess. However when running through my application in
release mode the application's (assemblyname.vhost.exe) memory usage
fluctuates heavily and goes upto a max of 1.5GB and then rests on 1GB once
the application is loaded. This does not occur in debug mode, it stays
around 370mb...

The memory does spike on the first call to the webservice, and it is WAAAY
to slow as its just doing a version check, (ie grabbing a small string
value)...

Does anyone have any ideas on where to look? What to check? how can I solve
this?

Thank you so much for any ideas anyone can shed on this
John Sheppard

 

[Michel Posseth [MCP]]

Well first of all get rid of the assemblyname.vhost.exe you should only
release the assemblyname.exe

vhost is a hosting process used by Visual Studio that improves debugging
performance, enables partial trust debugging, and enables design time
expression evaluation.


hth

Michel

 

[Leon Mayne]

Well first of all get rid of the assemblyname.vhost.exe you should only
release the assemblyname.exe

vhost is a hosting process used by Visual Studio that improves debugging
performance, enables partial trust debugging, and enables design time
expression evaluation.

Further to that, you can actually turn off the use of the vhost file by
unchecking "Enable the Visual Studio hosting process" in the Debug tab of
the project's properties. This should give you a more accurate look at how
long your app takes to run.

 

[John Sheppard]

Further to that, you can actually turn off the use of the vhost file by
unchecking "Enable the Visual Studio hosting process" in the Debug tab of
the project's properties. This should give you a more accurate look at how
long your app takes to run.

Ok, I have switched those off, it still takes up 1.2GB of ram and runs
considerably slower than in debugging mode (approximatly 200% slower)

I have tried looking at perfmon to see what is happening. I will post links
to images of those up so they can be seen if that will help. (its
interesting?

I will try build it on my vista box when I get home, see what happens then.

Any other thoughts? I have wrapped activex controls in the application is
that likly to be an avenue to scope out? The application is slow far before
any of those controls are used however.

Thank you SO much for your ideas, cause im kinda stumped...
John Sheppard

 

[Armin Zingler]

Any other thoughts? I have wrapped activex controls in the application
is that likly to be an avenue to scope out? The application is slow
far before any of those controls are used however.

http://www.microsoft.com/downloads/...1C-3870-43BE-8926-862B40AA0CD0&displaylang=en


Armin