We are adding a Java app (JBoss, Linux) to the existing 4GL (9.1D, custom web interface) app. I have done everything I can find to help (second broker, "update statistics", cut server load), but while the 4GL app runs OK, the SQL is very slow.
Some of this is SQL. (Progress handles "where A in (select ...)" better than any other db I've seen, sometimes better than a join.)
However, even statements like "select A from B where primary_key = x" are 10 times slower than another database with the same data, and a number of the Java features are too slow to run in a web application. The posts I've seen here suggest that the SQL is slow, but this is too slow. If I can't speed up the SQL, I'll have to use 4GL to get the data, and XML or something to get it to the Java.
Pointers?
We would also be willing to hire somebody to tune the db or point out my failings, but we sell to government and non-profits, so we are not rolling in money, and my boss would like some sort of guarantee of results before shelling out big bucks. (Low hourly, big bonus?) pphelan (a) footholdtechnology.com for details.
Some of this is SQL. (Progress handles "where A in (select ...)" better than any other db I've seen, sometimes better than a join.)
However, even statements like "select A from B where primary_key = x" are 10 times slower than another database with the same data, and a number of the Java features are too slow to run in a web application. The posts I've seen here suggest that the SQL is slow, but this is too slow. If I can't speed up the SQL, I'll have to use 4GL to get the data, and XML or something to get it to the Java.
Pointers?
We would also be willing to hire somebody to tune the db or point out my failings, but we sell to government and non-profits, so we are not rolling in money, and my boss would like some sort of guarantee of results before shelling out big bucks. (Low hourly, big bonus?) pphelan (a) footholdtechnology.com for details.