Jay Sprenkle wrote:

I'm glad to see someone is working on this since it was a very noticable problem for me.

I don't think it will matter what database you use if you're forced to have it hosted over a network. As far as I know they all rely on the underlying locking mechanism in the OS, which is inherently slow over a network.

Can you avoid multiple locking latency hits by just getting a lock at startup and never relinquishing it?
What about copying (importing) the network database to a ":memory:" database, and periodically copy (export) it back?

Reply via email to