Run full benchmarks weekly and auto-update perf table
See original GitHub issueThe full benchmark suite currently takes about 20 hours to run. This is onerous enough that the full benchmark isn’t run often. Ideally, we should have an automatic weekly run of the full benchmark suite that automatically generates a new performance table and creates a new github PR with the updated perf table in README.md
. This would keep our numbers honest and prevent bitrot or inadvertent bugs from creeping in undetected.
@lilleswing: Would it be feasible to use our Jenkins CI to do this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
SQL Server Statistics and how to perform Update Statistics in ...
Auto Update Statistics allows SQL Server to automatically update stats according to the predefined threshold; Updating statistics with FULL SCAN ...
Read more >Turn off Automatic Updates to Boost Performance - Tableau
To improve performance, you can turn off automatic updates while composing a view, and then query the data source when you're done.
Read more >Auto Create Statistics and Auto Update Statistics - {coding}Sight
When a user creates an index on a table, SQL Server optimizer by default creates statistics on the indexed column. If Auto Create...
Read more >Update Statistics,Performance Issue - MSDN - Microsoft
Hi,. We have Auto Update Statistics property of DBs set to true.I want to know If we have to do update statistics periodically...
Read more >SQL Server Auto Update and Auto Create Statistics Options
Solution. How do the statistics increase the performance of your SQL Server query execution? The statistical histograms are used by the Query ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah I’ll do that after I fix the diffing logic (it isn’t parsing the results.csv correctly right now)
Benchmarks now run weekly (or so) on Jenkins so going to go ahead and close this issue.