(Notice that the bug you referenced hasn't had any real progress since it was filed in August 2011, and work has stopped on the parent bug for integrating leveldb.)
I don't know much about the particular performance problem you're referencing, but I doubt it is as simple as sqlite not being fast enough.
This is some combination of slowness from pulling js from the cache, raw js speed, and indexedDB speed. I assumed it was mostly the latter but I could be wrong.
But I just ran the test suite again and after a few runs, there was little difference in timing, firefox even came faster a few times.
And this is in latest stable, I cant test nightly yet due to some api changes, and I know there was a lot of work done on idb performance improvements last week.
Pleasantly surprised
I hope this doesn't mean Firefox is going to stop working on it because their implementation is much slower than in Chrome and IE (albeit Chrome is using the old spec).