Note that there are some explanatory texts on larger screens.

plurals
  1. POSelecting number of threads in a multiprocess multiprocessor environment
    primarykey
    data
    text
    <p>I went through a few questions such as <a href="https://stackoverflow.com/questions/9038604/posix-threads-on-a-multiprocessor-system">POSIX Threads on a Multiprocessor System</a> and <a href="https://stackoverflow.com/questions/10089552/concurrency-of-posix-threads-in-multiprocessor-machine">Concurrency of posix threads in multiprocessor machine</a> and <a href="https://stackoverflow.com/questions/1713554/threads-processes-vs-multithreading-multi-core-multiprocessor-how-they-are">Threads &amp; Processes Vs MultiThreading &amp; Multi-Core/MultiProcessor : How they are mapped?</a> <pre> </pre></p> <p>Based on these and few other Wiki articles , I believe for a system having three basic works viz, Input , Processing and Output <pre> </pre></p> <ul> <li><p>For a CPU - bound processing number of CPU -intensive threads (No. of Application * Thread per application) should be apprx 1 to 1.5 times the number of cores of processor.</p></li> <li><p>Input and Output threads must be sufficiently large, so as to remove any bottlenecks. For example for a communication system which is based on query/query-ack and response/response - ack model, time must not be wasted in I/O waiting states.</p></li> <li><p>If there is a large requirement for dynamic memory, its better to go with greater number of processes than threads (to avoid memory sync ups).</p> <p>Are these arguments fairly consistent while determining number of threads to have in our application ? Do we need to look into any other paramters??</p></li> </ul>
    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.
 

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