worker-process

I am trying to deploy a .NET Web application to IIS (7.5) without any hassle for the users. I have made sure that Disable Overlapped Recycle is False but i still run into the same problem every time. Every time I upload new binaries for the site, IIS kills the worker process before it has started a new one. So every time I upload new binaries users get this error message: Server Error in '/' Application. Could not load file or assembly 'MyApplicationWeb' or one of its dependencies. The process cannot access the file because it is being used by another process. (Exception from HRESULT:

I want to use TPL in Worker process on Windows Azure. I'm looking to add an IJob the queue, this has a Run method, so the worker will consist of: loop get item off queue Use TPL to call IJob.Run, this is an async call But I'm a bit concerned about the maximum items I can add to TPL? I'm happy to build my own TPL Pool of some sort if required, just checking it capabilities. Cheers, Ash. Reed Copsey One of the main goals of the TPL is to remove the need to worry about this. By decomposing your work into Tasks instead of Threads, you're allowing the scheduler to handle the balancing of this more

I have a lot of Singleton implementation in asp.net application and want to move my application to IIS Web Garden environment for some performance reasons. CMIIW, moving to IIS Web Garden with n worker process, there will be one singleton object created in each worker process, which make it not a single object anymore because n > 1. can I make all those singleton objects, singleton again in IIS Web Garden? kervin I don't believe you can ( unless you can get those IIS workers to use objects in shared memory somehow ). This is a scope issue. Your singleton instance uses process space as its

We have a fairly high volume ASP.Net site written in c# using MS commerce server, running in a 32-bit environment. I see the worker process up to 980 megabytes quite often. I would like to profile this process and determine where any gains could be made in code to reduce the memory foot print of this site. My question what tools have worked well for you doing this sort of thing on ASP.Net web applications? I am looking for tools that will give me very specific feedback, that will really help to clearly see what needs to change in the code. It would be best if this tool could profile our

What is the best practice for deciding how many worker processes to allow for an ASP.NET web application? On one server I manage, creating a new AppPool defaults to 10 (maximum) worker processes. Other people suggest that the normal setting is one. What problem does multiple worker processes solve and what are the techniques for deciding on how many? Worker processes are a way of segmenting the execution of your website across multiple exe's. You do this for a couple of reasons, one if one of the workers gets clobbered by run time issues it doesn't take the others down. For example, if a html

I have one website on my server, and my IIS Worker Process is using 4GB RAM consistently. What should I be checking? c:\windows\system32\inetsrv\w3wp.exe I would check the CLR Tuning Section in the document Gulzar mentioned. As the other posters pointed out, any object that implements IDispose should have Dispose() called on it when it's finished with, preferably using the using construct. Fire up perfmon.exe and add these counters: Process\Private Bytes .NET CLR Memory# Bytes in all Heaps Process\Working Set .NET CLR Memory\Large Object Heap size An increase in Private Bytes while the number