Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you lower the level, the thread-pool will kill off threads which will (GoodThing™) reduce memory use (the stacks for all those threads), and (BadThing™) mean they have to be created again when you up the level again. It could also make the pool overly generous if there are lots of thread-pool-using tasks in the meantime (BadThing™) though it could well be that enough of them are blocking that the overall use of the pool is actually better (GoodThing™). Chances are though, that the use it is put to in that period is too low for it to make a differences (eh, IrrelevantThing™).</p> <p>In all, I'd probably just set the pool to be as high as I ever will need it for the busy periods when the application starts, and then leave it alone. Dropping the level during other periods is worth experimenting with if there are performance issues during the rest of the application's run, but unless the memory or thread-use is a concern during these periods I wouldn't, since those threads are going to be used again in the future after all. Just setting the level once is simpler, and simpler is always better except when you can explain why it isn't ("as simple as possible, but no simpler").</p> <p>Edit:</p> <p>I wrote the above as a straight answer to the question, but the other answers that suggest not touching max-threads at all are really on the money. If you <strong>really, really</strong> need a very large number of threads, create them yourself (and either don't pool, or handle pooling yourself, depending on the importance of spin-up time). But before that, look at alternatives as it's not the best approach much of the time either.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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