diff options
author | EuAndreh <eu@euandre.org> | 2023-03-30 14:22:11 -0300 |
---|---|---|
committer | EuAndreh <eu@euandre.org> | 2023-03-30 14:34:47 -0300 |
commit | 11f3daea8627effd0127b28d2d46fb53af49a7fc (patch) | |
tree | 29a181aa5396ef8ffeb25dac07bd7e9dad7e31fc /src/web/cgi | |
parent | backup.sh: Fix capture of $STATUS to the desired behaviour (diff) | |
download | toph-11f3daea8627effd0127b28d2d46fb53af49a7fc.tar.gz toph-11f3daea8627effd0127b28d2d46fb53af49a7fc.tar.xz |
src/infrastructure/scripts/report.sh: v2
Now instead of working through each commit searially, we build a graph
of steps and work on that by emitting make(1) code to be executed.
May this code prove to be diffucult to modify or extend, this is a valid
commit "checkpoint" to revert to in order to recover the *exact* same
behaviour, but simpler code.
Simple benchmarks suggest that:
- on a single core, the scrit is ~15% slower;
- with 2 cores it is as fast as the original;
- as more cores are added, the faster it gets, up to $(nproc) when
using more cores doesn't change anything.
That means that it is a useful optimization for our desktops, but a
hinderance for our current server, which only has a single core.
Diffstat (limited to 'src/web/cgi')
0 files changed, 0 insertions, 0 deletions