In my last post, I criticized e for being slow and bloated. As it turns out, e's sluggishness and high memory usage were being caused by an
e.db file that had grown too large. Once I removed the huge database and started fresh, e's performance improved dramatically and its memory usage returned to acceptable levels.
As far as I've been able to tell,
%APPDATA%\e\e.db is where e stores preferences and file history data. Over time, as more and more files are edited, this database grows, since it contains branching undo/redo data for every file you edit. The bigger it gets, the longer it takes e to start up and the more memory it appears to use.
E's author says that the memory usage reported by Task Manager includes non-paged virtual memory and isn't indicative of e's actual RAM usage, but he still hasn't responded to the question of why a large
e.db seems to have such a detrimental effect on startup time. He did suggest creating milestones every so often to clear a file's history, so I'll try that and see if it improves things.
In any case, e is running smoothly once more and I'm happy with it again. Hopefully the issues with
e.db will be resolved eventually, but for now they're a minor inconvenience offset by the fact that e is such a pleasure to use in almost every other regard.
Coincidentally, e 1.0 was released today. Get it while it's hot.