core: Opportunistic scheduler

0 votes

Vote

Raised 0% of 24 credits
(24 credits = 4 hours or $171.67)

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 usa…

Suggested by Chris Graham on 19th November 2019

core: Cache warm up via Cron

0 votes

Vote

Raised 0% of 180 credits
(180 credits = 30 hours or $1,287.56)

Initial installs may seem slow because initial caches are not populated.
Additionally, future use may seem slow if some resource is accessed but the cache is expired.

These caches could easily be populated in the background (in this priority order):
- Language file cache
- Template cache
- Comcod…

Suggested by Chris Graham on 19th November 2019

core: Re-review all indexes

0 votes

Vote

Raised 0% of 18 credits
(18 credits = 3 hours or $128.85)

Review all indexes in the system...

1) Is each necessary? Document why with a code comment. If not, remove (as indexes use disk space and slow writes).
2) Is *sorting* covered on a single index. For example, ideally an index on a category ID will also have a secondary index column on the timestamp, so…

Suggested by Chris Graham on 19th November 2019

core: Ensure we are using web font loader with Google Fonts

0 votes

Vote

Raised 0% of 12 credits
(12 credits = 2 hours or $85.84)

We must not have any Google Fonts blocking the critical rendering path.

Google does provide a solution for this:
https://www.lockedownseo.com/load-google-fonts-asynchronously-for-page-speed/

Suggested by Chris Graham on 10th June 2019