ORIGINAL: herwin
ORIGINAL: floydg
ORIGINAL: herwin
That's a standard problem with JDBC systems. You need to bug the developers to allow people to use alternative high-performance DBMSs.
Okay, I'm game - if it can improve performance, can you recommend something?
There are two problems--big databases are unavoidably slower, and the memory fragmentation you get in the JVM as you load a lot of data means you start thrashing. There was this FAA system I had some involvement with that ran into just that problem. I've asked the DBMS expert who sits two desks over for some suggestions.
For a starter, is the database normalised?
I believe the database is in 3NF.
The amount of data loaded is transient - once we get a "current" snapshot, the memory is freed, so in steady-state, the usage is relatively constant. The problem is building the current snapshot, which is the time killer.
Floyd








