Databases
StackOverflow2013
Postsdbo
POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
    primarykey
    data
    text
    <p>I've got a job processor which needs to handle ~300 jobs in parallel (jobs can take up to 5 minutes to complete, but they are <em>usually</em> network-bound).</p> <p>The issue I've got is that jobs tend to come in clumps of a specific type. For simplicity, let's say there are six job types, <code>JobA</code> through <code>JobF</code>.</p> <p><code>JobA</code> - <code>JobE</code> are network bound and can quite happily have 300 running together without taxing the system at all (actually, I've managed to get more than 1,500 running side-by-side in tests). <code>JobF</code> (a new job type) is also network-bound, but it requires a considerable chunk of memory and actually uses GDI functionality.</p> <p>I'm making sure I carefully dispose of all GDI objects with <code>using</code>s and according to the profiler, I'm not leaking anything. It's simply that running 300 <code>JobF</code> in parallel uses more memory than .NET is willing to give me.</p> <p>What's the best practice way of dealing with this? My first thought was to determine how much memory overhead I had and throttle spawning new jobs as I approach the limit (at least <code>JobF</code> jobs). I haven't been able to achieve this as I can't find any way to reliably determine what the framework is willing to allocate me in terms of memory. I'd also have to guess at the maximum memory used by a job which seems a little flakey.</p> <p>My next plan was to simply throttle if I get OOMs and re-schedule the failed jobs. Unfortunately, the OOM can occur anywhere, not just inside the problematic jobs. In fact, the most common place is the main worker thread which manages the jobs. As things stand, this causes the process to do a graceful shutdown (if possible), restart and attempt to recover. While this works, it's nasty and wasteful of time and resources - far worse than just recycling that particular job.</p> <p>Is there a standard way to handle this situation (adding more memory is an option and will be done, but the application should handle this situation properly, not just bomb out)?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeter Mortensen
    1. USBasic
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. USMathias
      1. VTFavorite
    3. VO
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPerhaps, you can check [Process.PrivateMemorySize64](http://msdn.microsoft.com/en-us/library/s80a75e5%28VS.80%29.aspx) or something similar before running a job
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. USHarvey Kwok
    2. CO@HarveyKwok Thanks, I'm aware of those (in fact, I report them to a central server with every "heartbeat" so I can keep an eye on things). The problem is, they only tell me what I'm using, not how much I _can_ use
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. USBasic
    3. COWhy don't you just assign a "cost" to a job. 1 for all cheap jobs, big number of the expensive one. Don't let another one start if the sum of active jobs is > 300.
      singulars
      1. POHandling an out of memory exception gracefully in .NET (or avoiding it entirely)
      1. USHans Passant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload