Question

I need the fastest way to periodically sync file with memory.

What I think I would like is to have an mmap’d file, which is only sync’d to disk manually. I’m not sure how to prevent any automatic syncing from happening.

The file cannot be modified except at the times I manually specify. The point is to have a checkpoint file which keeps a snapshot of the state in memory. I would like to avoid copying as much as possible, since this will be need to called fairly frequently and speed is important.

Answer 1

mmap can’t be used for this purpose. There’s no way to prevent data from being written to disk. In practice, using mlock() to make the memory unswappable might have a side effect of preventing it from getting written to disk except when you ask for it to be written, but there’s no guarantee. Certainly if another process opens the file, it’s going to see the copy cached in memory (with your latest changes), not the copy on physical disk. In many ways, what you should do depends on whether you’re trying to do synchronization with other processes or just for safety in case of crash or power failure.

If your data size is small, you might try a number of other methods for atomic syncing to disk. One way is to store the entire dataset in a filename and create an empty file by that name, then delete the old file. If 2 files exist at startup (due to extremely unlikely crash time), delete the older one and resume from the newer one. write() may also be atomic if your data size is smaller than a filesystem block, page size, or disk block, but I don’t know of any guarantee to that effect right off. You’d have to do some research.

Another very standard approach that works as long as your data isn’t so big that 2 copies won’t fit on disk: just create a second copy with a temporary name, then rename() it over top of the old one. rename() is always atomic. This is probably the best approach unless you have a reason not to do it that way.