Lines Matching refs:threads

7 When striving for performance, programming in terms of threads can be a
9 your program in terms of *logical tasks*, not threads, for several
31 The threads you create with a threading package are *logical* threads,
32 which map onto the *physical threads* of the hardware. For computations
37 threads to keep the physical threads working. *Oversubscription* occurs
38 when there are more running logical threads than physical threads.
40 threads, which incurs overheads as discussed in Appendix A, *Costs of
43 threads, in a way that tolerates interference by other threads from the
47 The key advantage of tasks versus logical threads is that tasks are much
48 *lighter weight* than logical threads. On Linux systems, starting and
70 number of threads, it is important to distribute work evenly across
71 those threads. As long as you break your program into enough small
73 threads to balance load. With thread-based programming, you are often
80    threads, and let the task scheduler choose the mapping from tasks to
81    threads.
84 Finally, the main advantage of using tasks instead of threads is that
87 threads to get good efficiency, because you have one logical thread per
89 have to deal with the relatively coarse grain of threads. With tasks,