4 ms·
In the embedded world the specifics often outweigh the general. Specifics like - what storage are you using? What clock does it run at? What page size are you u
by anitil 4y ago
In the embedded world the specifics often outweigh the general. Specifics like - what storage are you using? What clock does it run at? What page size are you using (you'd want to pass this to sqlite for best results)? What locks are you using? Is there a 1mS undocumented sleep on startup to allow some peripheral to stabilise that accidentally got pulled in to the main code path (has happened to me - the initialize function didn't set the initialized flag)?
I'd expect closer to 5uS than 5mS, but I'm not that familiar with the ESP32 devices
- johnboiles 4y agoIs your 5us number from experience? Have you run SQLite on embedded before? Just hoping to hear some real world performance numbers for any hardware remotely similar!
- anitil 4y agoI have run sqlite on a flash chip before (no filesystem, I suppose sqlite _was_ the filesystem) but I never took benchmarks. It was a 200MHz processor as well and it was basically fast enough out of the box that I never spent time on it. For 5uS response you have something like a thousand cycles to work with so any issue is likely storage related. I'd expect writes to be a bottleneck for example
- adql 4y agoI'm not getting 5us on gigahertz-clock CPUs. ESP32 isn't exactly demon of speed either compared to anything SQLite usually runs on