Hi Darren, and thanks for the replay
Darren Norris escribió:
HI,
Does this go back to a few other threads - where other users have picked up on
slow response times? Drew might remember better than me?
as I can remember there was a "Base performance" thread.
My specific question concerns the latest and stable releases: OOo 2.3.0,
Sun Report Builder 1.0.1.
The information provided by the user:
HSQLDB embedded, table with 20.000 records, seven fields (ID INT gen. by
def. ident., 3 numeric fields, 1 time field, 1 date field, and a
varchar field ).
The report is very simple: the data and the time fields, and a group
from a numeric field.
Once executed, the report seems to have 300 pages, but if you scroll
down, they turn to be circa 170.
When OOo start to generate the text document, all OOo open windows
freeze until it finish its job (from 5 to 2 minutes, depending of the
PC). If the user starts trying to set the focus on the different open
windows, title bars look as if OOo wasn't responding (every window icon
turns into the common "No response" icon under WinXP).
From what I have experienced doing anything with the HSQLDB engine (not sure
correct term but what ever is the backend nuts and bolts) where there are more
than a few hundred records is slow.
By doing 'anything' - I have only needed to run simple SQL (join and summarise multiple tables) which do go slow when there are more than a few hundred records - but I have not tested properly and have not tested the report builder. Oh -yes I am confident that the SQL is fine (e.g. the same query, against same tables runs in under a second in MySQL and takes 3 - 5 minutes in Base(v 2.3, using windows vista business)).
So I have started to use other free databases (MySQL, Postgre etc) to hold and manipulate data and occasionally use Base as a front-end to allow integration with spreadsheets, documents etc which is really great by the way!
I am not suggesting this approach is suitable for the 'average user' but it is just a description of what I had to do.
Here will be nice to know if this an HSQL problem (as discussed in the
thread "Base performance", where embedded db where mostly discussed), or
if it is a problem of the SRB.
Did try to build a report with the new SRB, connecting to MySQL or
Postgres (with a "big" table) ?
Darren
Bye and thanks,
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
