worker-process

问题 I have a query like below in PostgreSQL: UPDATE queue SET queue.status = 'PROCESSING' WHERE queue.status = 'WAITING' AND queue.id = (SELECT id FROM queue WHERE STATUS = 'WAITING' LIMIT 1 ) RETURNING queue.id and many workers try to process one work at a time (that's why I have sub-query with limit 1). After this update, each worker grabs information about the id and processes the work, but sometimes they grab the same work and process it twice or more. The isolation level is Read Committed.

问题 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

问题 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? 回答1: I don't believe you can ( unless you can get those IIS workers to use objects in

问题 In ASP.NET: How can I tell when the ASP.NET worker process last restarted? In ASP.NET, how can I tell when the app domain last recycled? 回答1: For the worker process, you can programmatically read Process -> Elapsed Time from the corresponding perf. counter (1) or directly from the System.Diagnostics.Process namespace; for the AppDomain , you can set an application-level variable at start-up to serve as your baseline and measure against that manually. Scott Mitchell actually has a couple of

问题 I need to understand something about ASP.NET session state, as it applies to IIS 7 and ASP.net 3.5. If an application is configured to use in-process session state, will that work OK if there are multiple worker processes? In other words, do worker processes share session state? The default configuration for IIS 7 is to use in-process session state and to allocate a maximum of 10 worker processes. It would seem likely then, that this default configuration should work. I'm dealing with a

问题 I've got a code base with lots of this: byte[] contents = FileUtils.FileToByteArray(FileOfGartantuanProportions); I don't control my IIS server, so I can't see the system log or do instrumentation, I just get to see my request fail to return (white page of death) and sometimes YSOD with Out of Memory error. Does anyone have a rule of thumb for what is the most data you can load up into memory before IIS5 or IIS6 will kill the work process or just keel over and die? Or better yet, is there an

问题 I've noticed as my website gets bigger and bigger, the time my laptop takes to display my page is much longer then say a new projects with minimal references. I think there are two variables at play that affect ASP.NET warm-up time: The quantity of external references The time it takes for a worker process to new() up each instance per worker process Additional time for the WCF objects as the ServiceHost may be in an external DLL First, are those the correct variables to take into account

问题 In perfmon in Windows Server 2003, there are counter objects to get per-process processor time and memory working set statistics. The only problem is that in an environment with multiple application pools, there is no way to reliably identify the correct worker process. In perfmon, they are all called "w3wp", and if there is more than one, they are w3wp, w3wp#1, w3wp#2, and so on. Even these names are unreliable - the number depends on which one started first, and obviously changes when an

问题 We are having issues with IIS6 slowdowns when using more than 1.2GB of RAM in a single worker and would like to use more workers. However looks like ASP sessions are made by worker and when the browser accesses some page through another worker it losts the ASP session. Do you have some tips on how to solve this problem? We are considering to use some other way to manage session separately from IIS (not database, maybe memcache?). Do you recomend something? Note.: The application is full of

问题 I have a very weird problem with one of my IIS application pool processes. Ive been getting a System.OutOfMemoryException error lately and ive been trying to figure out exactly what is going on. Basically I have a script that uses a web service to get a file from our DAM. It then checks the file stores it a byte array, then uses the Response to output the file. The only one ive been having problems with is the PDF's when they are over 20MB now it seems that they cause an error sometimes. If I