View Single Post
Old 03-16-2018, 11:47 AM   #8
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 35,393
Karma: 145435140
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by aurne View Post
Thanks! That's pretty informative, though it seems like a really non-standard way to handle databases. The wiki quotes "maximum performance" as justification. Do you, or anyone else have any numbers regarding the performance differential between in-memory and traditional sqlite?
Not sure how relevant to sqlite this is but Microsoft's SQL 2014 and 2016 have the capability to use in-memory OLTP. Various tests showed a 30x increase in performance depending on what your task mix is. You just need lots of memory to hold the database -- in our case, the SQL servers have 1TB of memory with a flash SAN for disk storage.
DNSB is offline   Reply With Quote