Skip to content

Performance comparison of SQLite parse_number extensions in C and Rust

What happened

AI digest

On 9 November 2026, Simon Willison published a performance comparison of four SQLite extensions implemented in C and in Rust, all with the same parse_number() behaviour. The optimised C version took 16–19 ns per row, roughly twice as fast as the Rust version and far faster than SQL's replace(). The report mentions no later updates or differing accounts.

Written by AI from the reports · updated 5 d ago

Timeline

Follow the reports to see the event from each side.

Nov 9
  1. Simon Willison
    parse_number() as a SQLite extension: C vs Rust

    Research: parse_number() as a SQLite extension: C vs Rust I was out walking the dog when I got curious about how easy/difficult it would be to write a SQLite C extension that adds a parse_number() function for turning strings like -$1,234.56 or '12.5%' into numeric values that could be summed and sorted.

Heat of this event

Current heat 3·Peak in the comparable range 9(Nov 9 09:00)·Change over 24 hours in the comparable range -51%

02.557.510Nov 909:00Nov 1000:00Nov 1015:00Nov 1106:00

The trend compares only the same accounts observed without a break, so its range can be narrower than the current heat count. Move the pointer or tap the chart to see each hour; with a keyboard, use the left and right arrow keys.