Hacker News new | past | comments | ask | show | jobs | submit login

FWIW, storage is cheap, but caches are not.



It's cheap if the cache is also on SQLite. Might not even need a separate db for some use cases.

This runs on python and works with several backends including SQLite. https://requests-cache.readthedocs.io/en/stable/


I meant hardware caches like L1, L2, and L3 on the CPU.

SQLite is used in some HPC work.

ISO-8601 datetime strings can easily wreck your L1 cache. Instead of filling an eighth of the cache with a 64-bit value, you wind up filling almost half with a 27-character-long string.


I learned something new, thanks for sharing!

What format works well for hardware caching?


yw :-)

As small as you can tolerate tbh. The game is played by keeping data as small as possible and ensuring that related data has good locality in memory.

The gap between how fast your CPU works and how fast data can be retrieved from RAM is enormous.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: