View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001608 | Issue 8 drafts | Base Definitions and Headers | public | 2022-10-14 11:27 | 2024-06-11 09:12 |
Reporter | dannyniu | Assigned To | |||
Priority | normal | Severity | Comment | Type | Enhancement Request |
Status | Closed | Resolution | Accepted As Marked | ||
Product Version | Draft 2.1 | ||||
Name | DannyNiu/NJF | ||||
Organization | Individual | ||||
User Reference | |||||
Section | sysconf | ||||
Page Number | -- | ||||
Line Number | -- | ||||
Final Accepted Text | 0001608:0006008 | ||||
Summary | 0001608: Suggesting informative texts for bug-id339 | ||||
Description | Although creating as many threads as there are CPU cores is a simple way to maximize CPU usage, there are subtleties that make it not always the case. As explained in my proposed addition texts in the desired action. | ||||
Desired Action | Add informative texts to appropriate sections in sysconf: Although the queries _SC_NPROCESSORS_CONF and _SC_NPROCESSORS_ONLN provide a way for a class of "heavy-load" application to "guess" the optimal number of threads that can be created to maximize CPU usage, real-world environments have complications that affects the actual efficiency that can be achieved. For example: - there may be more than one "heavy-load" application running on the system, - the system may be battery power, and applications should co-ordinate with the system so as to ensure long-running task can pause, resume, and successfully complete even in the event of power outage. In case where a strictly standard-conforming instance of "heavy-load" application wants to avoid the use of vendor-specific APIs, they may wish to create threads based on the logical partition of the long-running task, or utilize heuristics such as the ratio between execution-time and real-time. | ||||
Tags | issue8 |
|
After D2.1 page 2061 line 66817 section sysconf(), add:Although the queries _SC_NPROCESSORS_CONF and _SC_NPROCESSORS_ONLN provide a way for a class of "heavy-load" application to estimate the optimal number of threads that can be created to maximize throughput, real-world environments have complications that affect the actual efficiency that can be achieved. For example: |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-10-14 11:27 | dannyniu | New Issue | |
2022-10-14 11:27 | dannyniu | Name | => DannyNiu/NJF |
2022-10-14 11:27 | dannyniu | Organization | => Individual |
2022-10-14 11:27 | dannyniu | Section | => sysconf |
2022-10-14 11:27 | dannyniu | Page Number | => -- |
2022-10-14 11:27 | dannyniu | Line Number | => -- |
2022-10-20 15:42 | geoffclare | Relationship added | related to 0000339 |
2022-10-20 15:58 | geoffclare | Note Added: 0006008 | |
2022-10-20 15:59 | geoffclare | Final Accepted Text | => 0001608:0006008 |
2022-10-20 15:59 | geoffclare | Status | New => Resolved |
2022-10-20 15:59 | geoffclare | Resolution | Open => Accepted As Marked |
2022-10-20 15:59 | geoffclare | Tag Attached: issue8 | |
2022-11-08 14:45 | geoffclare | Status | Resolved => Applied |
2024-06-11 09:12 | agadmin | Status | Applied => Closed |