Currently my PrintJobHistory plugin use a local sqlite3 database for storing the print job attributes, except the thumbnail and camera snapshot images. These images were located in the plugin data directory as single jpg files
I want to add an option to use an external database located on a different server. Now I am thinking of moving also the image data to the database. But what are the drawbacks:
- Browser-Performance: Currently you can list more then 200 Table-Entries with images and scroll thru that list "quickly". Because the image data is directly streamed from the filesystem.
Do you have experience or an opinion how I should handle storing the images and also providing fast responses.
Maybe setup a cache during startup. Loading images from the database into the Octoprint-Server, instead of "on demand".
Thx, in advance