Comment 2 for bug 907676

Eduardo> I've created a prototype of SQLite backend. Caveat: I compared a prototype to an optimized system, results are a little bit skewed.

With the current system, after every modification, you have to save your data. (That's the reason for this bug) Committing after each change is really slow. With my data, XML backend was about 1/2 time of SQLite backend. I also violated SQLite library by disabling thread checking because every modification is stored by a different thread -- re-opening SQLite would be even slower.

Yes, we might spend awful much time to optimize system for SQLite. It would be wasting of our time. GTG needs just toserialize data on a disk in some format - XML, JSON, plain text would be enough for that. SQLite adds too much overhead which we don't need at all.

Result: SQLite isn't a scalable backend for our usecase.

You can play with my prototype here: lp:~gtg-user/gtg/sqlite