>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? > > If it's large, like he mentioned, that will take a while. It sounds like it needs to be profiled to see what the slow parts are.
-- --- The Castles of Dereth Calendar: a tour of the art and architecture of Asheron's Call http://www.lulu.com/content/77264
