SmallWiki Persistence

It appears to me that the only SmallWiki persistence mechanism so far is to save the entire image. Is that correct? I'd like a persistence mechanism a bit more like that of WikiWorks. Having used WikiWorks for a long time, I'd like to improve upon it. In particular, file names should be meaningful, and all the versions of a page should be stored in one file. It should be easy to delete past history. The file format should make the system very tolerant of crashes. It should be plain text and easy to edit with any text editor. wiki.cs.uiuc.edu has 33 wikis on it. Most of them are small, but at least three of them have several thousand pages apiece. The image is over 100 meg, since all pages are stored in memory (like SmallWiki). When the machine pages, I will buy more memory. It gets several hits a second, all day long. It runs for several months between reboots. I need a persistence mechanism that can handle this. -Ralph Johnson