sshelve Write Caching

[generalfault]

It seems that shelve caches writes until close or sync (this means huge performance.)

sshelve seems like it should be a drop-in replacement, but instead of caching (or having an option to do so) it does a "sync" (or commit) after every write or delete. It does seem to cache for reads, but that is only half the story.

I do know of the "update" method, but that means complete rewrite of the logic of the programs that use shelve.

I don't think it would be too difficult to implement the caching, and I'm willing to write it, but I guess the question is... is there a reason this was specifically left out?

[jfennell]

This wasn't a drop-in for me so I did update instead and kinda departed from the usual semantics (I didn't want to have to worry as much about memory blowing up on me and that was pretty explicit with the calls to update()).

I generally prefer the update() approach as there is less distance between you writing something and potential errors from actually writing it to disk, but I don't have a specific reason for not doing the general shelve approach.

So, go ahead ^_^.