Nah dont work like that.
wish it did. here's pseudocode of what needs to be done.
What step of the process takes so long?
And what is done in this 3msec?
You could work with in memory hash tables.
it's not the size of the database it's thenumber of transactions. try hitting sqlite with 3 GB of transactions and see what happens
There are few relational databases that run 3Gig transactions in less than 3 msecs
so in your case indeed that might not be the solution.
[update on hashlist]
Quick test on XP: 3M hash entries.
2M lookups take a little less than 1 second.