I took 10078ms (=nearly the timeout duration) to fail.
What took so much CPU is this loop which doesn't do anything
while ((ft == null) && ((state != FINISH) && (state != STOP))) {
yield(); // let the parser run ... this is being called from
if (d.before(Calendar.getInstance().getTime())) {
exception = new SAXException("Timeout");
state = STOP;
}
}
Sorry for the personnal reply and thank you for your help
Gerald
2007/6/20, Andrea Aime <[EMAIL PROTECTED]>:
> Gérald Quintana ha scritto:
> > The sample Streams.xml contains 2 features, buffer size of 10 features
> > should be enough.
> > Setting the buffer size to 1000 doesn't help.
> > CPU load is 100%
>
> Then fire up a profiler and determine why it's slow :)
> And please, keep the mails on the users mailing list.
> Cheers
> Andrea
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
