Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When you use an <code>ExecutorService</code> you submit <code>Runnable</code> jobs to a thread-pool that are run in turn by the threads in the pool. You could do one of the following:</p> <ol> <li><p>Have each <code>Runnable</code> sit in a loop, dequeueing from a <code>BlockingQueue</code> in a loop to process each packet. That might be easier than all of them synchronizing around your buffer object. Something like:</p> <pre><code>public void run() { while (!shutdown) { packet = packetQueue.take(); processPacket(packet); } } </code></pre></li> <li><p>Alternatively, you can submit each packet to the thread-pool as a job itself although that might increase your object load. You could process each packet, extract the payload, and create a <code>Runnable</code> wrapper around the payload with the <code>run()</code> method which processes the payload. The contents of the <code>Runnable</code> class would be something like:</p> <pre><code>Payload payload; public void run() { // process packet here processPayload(payload); } </code></pre></li> </ol> <p>With both mechanisms, I'd choose a fixed thread number that best matches your number of processors and the nature of the processing task. The below example uses the number of processors but you might want to take a couple off for GC or other tasks. You might want to put more on in case the processing blocks on other IO. Only performance testing will tell you what the optimal value is there.</p> <pre><code>// start a pool that uses the number of threads that there are processors ExecutorService threadPool = Executors.newFixedThreadPool( Runtime.getRuntime().availableProcessors()); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POJava ThreadPool for multiple identical tasks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGray
    1. USGray
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJava ThreadPool for multiple identical tasks
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO#1 seems contrary to the spirit of thread-pool -- dispatching units of work to a pool of up to N threads. Instead, you're spinning up all N threads (where N = max pool size), and each one sits and waits on the queue until work comes in. If done this way, you might as well just create N threads directly and skip the thread pool entirely.
      singulars
      1. PO
      1. USJimN
    2. COOne more thing -- as written, your shutdown strategy for #1 doesn't quite work as the thread may wait forever on the packet queue and never re-inspect "shutdown" and terminate. In this case, I typically use a "poison pill" approach to signal that the thread should terminate.
      singulars
      1. PO
      1. USJimN
    3. COReally any task that requires threads will be improved with a thread-pool @Jim. Even in case #1.
      singulars
      1. PO
      1. USGray
 

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