On 05/22/2015 02:37 PM, Mikael wrote: > Hi, > > If mmap_size is big enough, read() will never be needed, so what about > enabling mmap on platforms that "lack of a unified buffer cache"? > > I mean, on a 64bit platform, setting mmap_size to say 1TB should be fine - > > So what about enabling mmap_size on platforms that "lack of a unified > buffer cache"? > > > Also, if read() by some reason would be needed, there's msync() which is > like a flush(), so here the "lack of a unified buffer cache" shouldn't be > an issue anyhow?
I think part of the concern is two processes accessing the same SQLite database - one using mmap() and one using regular read() and write() calls. Just out of interest, is it a specific platform that you're concerned about? Dan.
