Databases
StackOverflow2013
Postsdbo
POJava thread creation overhead
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava thread creation overhead
    primarykey
    data
    text
    <p>Conventional wisdom tells us that high-volume enterprise java applications should use thread pooling in preference to spawning new worker threads. The use of <code>java.util.concurrent</code> makes this straightforward.</p> <p>There do exist situations, however, where thread pooling is not a good fit. The specific example which I am currently wrestling with is the use of <code>InheritableThreadLocal</code>, which allows <code>ThreadLocal</code> variables to be "passed down" to any spawned threads. This mechanism breaks when using thread pools, since the worker threads are generally not spawned from the request thread, but are pre-existing.</p> <p>Now there are ways around this (the thread locals can be explicitly passed in), but this isn't always appropriate or practical. The simplest solution is to spawn new worker threads on demand, and let <code>InheritableThreadLocal</code> do its job.</p> <p>This brings us back to the question - if I have a high volume site, where user request threads are spawning off half a dozen worker threads each (i.e. not using a thread pool), is this going to give the JVM a problem? We're potentially talking about a couple of hundred new threads being created every second, each one lasting less than a second. Do modern JVMs optimize this well? I remember the days when object pooling was desirable in Java, because object creation was expensive. This has since become unnecessary. I'm wondering if the same applies to thread pooling.</p> <p>I'd benchmark it, if I knew what to measure, but my fear is that the problems may be more subtle than can be measured with a profiler.</p> <p>Note: the wisdom of using thread locals is not the issue here, so please don't suggest that I not use them.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USskaffman
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    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. POJava thread creation overhead
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJava thread creation overhead
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJava thread creation overhead
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI was going to suggest that wrapping your ThreadLocal in an accessor method would probably solve your issues with InheritableThreadLocal, but you don't seem to want to hear that. Plus, it seems that you're using InheritableThreadLocal as an out-of-band call frame, which, to be honest, seems like a code smell.
      singulars
      1. POJava thread creation overhead
      1. USkdgregory
    2. COAs far as thread pools go, the main benefit is control: you know that you won't suddenly try to spin up 10,000 threads in a second.
      singulars
      1. POJava thread creation overhead
      1. USkdgregory
    3. CO@kdgregory: For your first point, the ThreadLocals in question are used by Spring's bean scoping. That's the way Spring works, and not something I have control over. For your second point, the inbound request threads are limited by tomcat's thread pool, so the limiting is inherent in that.
      singulars
      1. POJava thread creation overhead
      1. USskaffman
 

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