View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003958 | Composr | core | public | 2019-11-19 01:12 | 2024-07-23 16:57 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003958: Opportunistic scheduler | ||||
| Description | Some background Cron hooks are not very time critical, but may have a performance impact. Ideally we would run these hooks only when the server is under low load. Code in a detector function to find if the server is under 'low load', based on I/O load, CPU usage (uptime command on Linux), and memory usage (configurable thresholds). This check would be run before every Cron hook that is algorithmically determined as 'optional'. Make the scheduler (Composr CRON system) use this to determine whether some low priority hooks should get done. For example, updating the sitemap. CRON hooks would specify: - a "frequency" (currently this logic is hard-coded in v10, and already implemented as the 'minutes_between_runs' setting in v11) - a "fluff" factor (to determine how much things should be allowed to be late, e.g. 1.6x -- tasks being deferred if not in a low load state) - a "priority" (i.e. tasks would run in priority order [well actually anything already late past it's fluff factor would be elevated to high priority]) ...and the system would automatically launch CRON hooks accordingly. Hooks should be able to keep calling back and checking to see if they should keep going. Not all hooks would implement that, but particularly long running low priority re-entrant ones (background caching/indexing) would. | ||||
| Tags | Type: Performance | ||||
| Time estimation (hours) | 4 | ||||
| Sponsorship open | |||||
| related to | 0003501 | resolved | Patrick Schmalstig | Poor-mans-Cron |
| related to | 0002236 | closed | Chris Graham | Opportunistic scheduler and background caching |
| related to | 0003959 | non-assigned | Cache warm up via Cron | |
| related to | 0003185 | non-assigned | Pagination indexing table specifically for forum topics | |
| related to | 0003288 | resolved | Chris Graham | Major overhaul of fulltext search support, the "Composr fast custom index" |
| related to | 0005656 | resolved | Patrick Schmalstig | Optimise task queue more intelligently |
|
|
The UI should probably indicate when a hook has been "deferred" and its reasoning. If a hook is deferred beyond the fluff factor, then Health Check should warn of this along with the UI. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-11-19 01:12 | Chris Graham | New Issue | |
| 2019-11-19 01:12 | Chris Graham | Tag Attached: ocProducts client-work (likely) | |
| 2019-11-19 01:12 | Chris Graham | Tag Attached: Type: Performance | |
| 2019-11-19 01:13 | Chris Graham | Relationship added | related to 0002236 |
| 2019-11-19 01:13 | Chris Graham | Relationship added | related to 0003501 |
| 2019-11-19 01:14 | Chris Graham | Relationship added | related to 0003959 |
| 2019-11-19 01:16 | Chris Graham | Relationship added | related to 0003185 |
| 2019-11-19 01:17 | Chris Graham | Relationship added | related to 0003288 |
| 2019-11-19 01:19 | Chris Graham | Description Updated | View Revisions |
| 2021-04-06 01:29 | Chris Graham | Tag Detached: ocProducts client-work (likely) | |
| 2024-07-23 14:57 | Chris Graham | Relationship added | related to 0005656 |
| 2024-07-23 16:57 | Patrick Schmalstig | Note Added: 0008897 |
