[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
howtos:hardware:processor_affinity [2013/01/13 18:04 (UTC)] – [Processor affinity] hazelhowtos:hardware:processor_affinity [2013/01/13 18:09 (UTC)] – [Processor affinity] hazel
Line 17: Line 17:
 Because the scheduler will do its best to keep processes running on the same CPU (as long as this is beneficial to overall performance) you usually do not have to interfere. However, some cases warrant pinning a process to a single CPU or a predefined subset. Let's look at two examples; the second will be discussed in more detail. Because the scheduler will do its best to keep processes running on the same CPU (as long as this is beneficial to overall performance) you usually do not have to interfere. However, some cases warrant pinning a process to a single CPU or a predefined subset. Let's look at two examples; the second will be discussed in more detail.
  
-  - Commercial database vendors like [[http://www.oracle.com/products/database/overview/|Oracle DB]] or [[http://www-01.ibm.com/software/data/db2/|IBM DB2]] want you to pay per CPU. Typically, database servers have a massive amount of CPU cores and you want to be able to decide how much to pay for your database (more performance would mean, more cost)+  - Commercial database vendors like [[http://www.oracle.com/products/database/overview/|Oracle DB]] or [[http://www-01.ibm.com/software/data/db2/|IBM DB2]] want you to pay per CPU. Typically, database servers have a massive amount of CPU cores and you want to be able to decide how much to pay for your database (more performance would mean more cost)
   - One process on a busy server is eating so many of your multi-CPU processor cycles that other programs' performance starts to suffer. Limiting your runaway process to a single CPU will free up resources for your other programs.   - One process on a busy server is eating so many of your multi-CPU processor cycles that other programs' performance starts to suffer. Limiting your runaway process to a single CPU will free up resources for your other programs.
  

Trace:

howtos:hardware:processor_affinity ()