miniblog.

← Back to all posts
Jan 11, 2015 at 23:36
SPEC benchmarks depend on undocumented C behaviour: http://t.co/9zkybqwM9N -- compiler benchmarking takes real language lawyering.

Related Posts

Dec 1, 2022 at 03:58
Benchmarking the cost of array bounds checks in Rust code: https://blog.readyset.io/bounds-checks/ The author even patches rustc to make sure *all* bounds checks are gone, in order to compare the performance!
Readyset | Drop-in SQL Caching for PostgreSQL and MySQL
Readyset | Drop-in SQL Caching for PostgreSQL and MySQL
Increase the scale of your PostgreSQL and MySQL deployment by up to 100x with Readyset - all without modifying your application code or database. Start using Readyset today for free!
Jan 26, 2022 at 08:27
Cute benchmarking technique for choosing sample programs in a benchmarking suite: perform principal component analysis to avoid redundancy!
rfcs/accepted/benchmark-suite.md at main · bytecodealliance/rfcs
rfcs/accepted/benchmark-suite.md at main · bytecodealliance/rfcs
RFC process for Bytecode Alliance projects. Contribute to bytecodealliance/rfcs development by creating an account on GitHub.
Jan 16, 2022 at 00:57
I really like instruction counts for measuring performance. It's not perfect, but it's a very stable metric, even if I'm listening to music whilst developing and benchmarking.