How Do SQLite and DISQLite Compare for a Large Simple Database?

AFAIR, DISQLite uses the obj files of Sqlite, and compile them with Delphi and produce more features than the original one, and using the same sqlite DB format, hence you can read the DISQLite database file by it by other languages that has support for Sqlite drivers.

Also one more feature with DISQLite you don't have to distribute the Sqlite DLL.

DISQLite support database size up to 2TB, so it could handle your requires without problems.

Another options I would consider is FireBird embedded version,and if you would like to scale it more, you can change to full FireBird server without much effort.

But I think both Sqlite & DISQLite will perform better than Firebird.

I use Audcom Sqlite components to access Sqlite databases, and you can compile it with Sqlite objs file so you will not have deploy sqlite dll.

I can suggest you writing your own implementation. If you don't need complex SQL queries, the simplest (and probably the fastest) implementation is file-based storage.

DISQLLite has two versions with the free one limited to personal and non-commerical usage. So this could be one of the deciding factor as SQLite is free opensource implementation without free/paid versions.

Both of the database would be able to handle data ranging in GBs. SQLite is available in pre-compiled binary i.e. DLL which can be distributed along your application. However, with the source code available you can also compile it within your application and use it without the need for DLL.

The advantage of using the DLL module (at times) is when some of the bugs are resolved you would simply be required to replace the DLL at the client machine instead of recompiling the whole application.

I feel SQLite would be a better option for yor requirement. Speed of database is not entirely based on the type of database. Hardware like harddisk access speed, available processing power, RAM etc also play an important role in speeding up database.