Is it possible to configure MySQL so only library updates are written to disk? Watched status, bookmarks and other non-critical data would remain in the memory buffer.
My rudimentary understanding of MySQL is that the MyISAM engine will cache queries until its key_buffer reaches its allotted size or until the system otherwise runs out of memory. SD Card speeds are slow, but I imagine that the entire library could be cached to RAM for read queries. The SD Card read speed would only be an issue upon loading the libraries for the first time, which should be rare on a 24/7 server.
The issue is SD Card longevity. Library updates are essentially a write-once, read-many times scenario, so that isn't an issue. Watched status, bookmarks and add-on related data are always changing. I don't know how often the disk is written, but this data isn't critical and could easily live entirely in memory.
Are there any MySQL gurus out there who can offer some insight on how to do this? I was thinking about resorting to hosting the engine on a ramdisk and storing a backup of the library database on disk for the inevitable reboot. Is there a more elegant way?
My rudimentary understanding of MySQL is that the MyISAM engine will cache queries until its key_buffer reaches its allotted size or until the system otherwise runs out of memory. SD Card speeds are slow, but I imagine that the entire library could be cached to RAM for read queries. The SD Card read speed would only be an issue upon loading the libraries for the first time, which should be rare on a 24/7 server.
The issue is SD Card longevity. Library updates are essentially a write-once, read-many times scenario, so that isn't an issue. Watched status, bookmarks and add-on related data are always changing. I don't know how often the disk is written, but this data isn't critical and could easily live entirely in memory.
Are there any MySQL gurus out there who can offer some insight on how to do this? I was thinking about resorting to hosting the engine on a ramdisk and storing a backup of the library database on disk for the inevitable reboot. Is there a more elegant way?