A Java Geek weekly 44

Last December, Log4Shell shortened the nights of many people in the JVM world. Worse, using the earthquake analogy caused many aftershocks after the initial quake. I immediately made the connection between Log4Shell and the Security Manager. At first, I didn’t want to write about it, but I’ve received requests to do so, and I couldn’t walk away.

1. SQLite is competitive with, and usually faster than, blobs stored in separate files on disk, for both reading and writing.
2. SQLite is much faster than direct writes to disk on Windows when anti-virus protection is turned on. Since anti-virus software is and should be on by default in Windows, that means that SQLite is generally much faster than direct disk writes on Windows.
3. Reading is about an order of magnitude faster than writing, for all systems and for both SQLite and direct-to-disk I/O.
4. I/O performance varies widely depending on operating system and hardware. Make your own measurements before drawing conclusions.
5. Some other SQL database engines advise developers to store blobs in separate files and then store the filename in the database. In that case, where the database must first be consulted to find the filename before opening and reading the file, simply storing the entire blob in the database gives much faster read and write performance with SQLite. See the Internal Versus External BLOBs article for more information.