Insert Benchmark results for MyRocks, InnoDB and Postgres.
Postgres is still boring, as it was for sysbench. I did not find serious regressions. With one exception, version 13.1 was faster & more efficient than 11.10. The exception was for loads with secondary index maintenance.
Conversation
Replying to
I myself put the Postgres index dedup secondary index regression at 2%-3% using the insert benchmark, which is slightly less than what you found (even referenced this in commit message). You can disable dedup using 'deduplicate_items' storage param when necessary, of course.
I like to think that my general approach to indexing enhancements contributed to the overall lack of regressions since 11. I try to structure enhancements as subtracting old harmful behaviors, not adding new helpful behaviors. The distinction is subtle, but seems important.
1
3
Replying to
That approach seems to be working.
I like the idea of triggering vacuum based on inserts because something has to set those vis map bits. Does insert-triggered vacuum do more work than it needs to do?
1
1
Show replies
Replying to
Thanks, I will repeat a test with insert-triggered vacuum configured to be unlikely and dedup disabled.
2