Re:SQLite small blob storage: 35% Faster Than the Filesystem
by notacoward on Wednesday June 14, 2017 @12:20AM
(#14550622)
FYI, in sqlite is still on disk.
[ Parent
| on HN ]
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by elchief on Wednesday June 14, 2017 @12:21AM
(#14550629)
It doesn't have to be. There's an in-memory option
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by Myrth on Wednesday June 14, 2017 @12:55AM
(#14550732)
I wonder if ram fs would perform exact the same as sqlite in memory.
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by DaiPlusPlus on Wednesday June 14, 2017 @03:18AM
(#14551174)
The article speculates that the overhead of calling `fopen` for each file and subsequently reading it is more expensive than reading from an already opened database file.
But as for how expensive `fopen` is really depends many factors.
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by kccqzy on Wednesday June 14, 2017 @03:41AM
(#14551233)
I would believe ramfs would be slower, as there will be additional system calls needed.
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by notacoward on Wednesday June 14, 2017 @07:49AM
(#14552034)
Filesystems can be built in memory (ramdisks) too, but comparing sqlite in memory to files on disk would be pretty silly. For any serious and fair comparison, in sqlite still means on disk.
Re:SQLite small blob storage: 35% Faster Than the Filesystem
by microcolonel on Wednesday June 14, 2017 @10:17AM
(#14552872)
For what it's worth, I think Mapbox's vector tiles can be stored in around 48GiB of RAM, which is perfectly within reason for a server. It's also the sort of data which is simple to shard. They can have multiple geolocated databases for a local area, and maybe fewer for international queries. This can be done pretty simply at the load balancer level.