feat: curioweb: Improve task_history indexes

[magik6k]

Related Issues

Proposed Changes

• clusterMachineSummary is a few % faster, not much impact on that query (takes 1.5s, so probably will warrant more optimizations at some point)
• clusterTaskHistorySummary went down to 100ms from waay-too-slow 5s+

Additional Info

clusterMachineSummary

EXPLAIN (ANALYZE, BUFFERS)
SELECT hist.completed_by_host_and_port, hist.name, hist.result, count(1)
FROM harmony_task_history hist
WHERE hist.work_end > now() - INTERVAL '1 day'
GROUP BY hist.completed_by_host_and_port, hist.name, hist.result
ORDER BY completed_by_host_and_port ASC;

Sort  (cost=16296.23..16296.98 rows=300 width=575) (actual time=1611.633..1611.634 rows=14 loops=1)
  Sort Key: completed_by_host_and_port
  Sort Method: quicksort  Memory: 26kB
  ->  HashAggregate  (cost=16280.88..16283.88 rows=300 width=575) (actual time=1611.601..1611.605 rows=14 loops=1)
"        Group Key: completed_by_host_and_port, name, result"
        ->  Index Only Scan using harmony_task_history_work_index on harmony_task_history hist  (cost=0.00..15004.03 rows=127685 width=567) (actual time=1.217..1608.701 rows=3569 loops=1)
              Index Cond: (work_end > (now() - '1 day'::interval))
              Rows Removed by Index Recheck: 1273329
              Heap Fetches: 0
Planning Time: 0.816 ms
Execution Time: 1611.763 ms
Peak Memory Usage: 98 kB

clusterTaskHistorySummary

EXPLAIN (ANALYZE, BUFFERS) SELECT id, name, task_id, posted, work_start, work_end, result, err, completed_by_host_and_port FROM harmony_task_history ORDER BY work_end DESC LIMIT 15

Limit  (cost=0.00..1.80 rows=15 width=631) (actual time=1.152..1.171 rows=15 loops=1)
  ->  Index Scan using harmony_task_history_work_index on harmony_task_history  (cost=0.00..153223.48 rows=1276854 width=631) (actual time=1.151..1.163 rows=15 loops=1)
Planning Time: 0.084 ms
Execution Time: 1.237 ms
Peak Memory Usage: 24 kB

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green