[
https://issues.apache.org/jira/browse/DERBY-5555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steffen Kuche updated DERBY-5555:
---------------------------------
Description:
Sounds incrediable? Test it by yourself with the attached program.
The issued reased up because of AMQ-3644, but it is actually a derby problem so
I post the issue here as well.
Derby writes multiple gigabyte of temporary files in its tmp directory during
one select statement. Afterwards these temporary files are deleted and rebuild
by the next Statement.
You can find a Test-Program (import it as a Maven-Eclipse project) which
reproduces this issue.
This program creates a derby database with the activemq Message table and fills
it with data (2000 Messages, this can take several hours). I assumed 3MB for
one message as our messages contain same binary data and has an average size of
3MB.
After the database is built one time a Statement and another time a
PreparedStatment is used to retrieve the next messages.
The Statement takes about 1 ms and the PreparedStatement about 258805 ms. Also
the second PreparedStatement takes as much time.
was:
Sounds incrediable? Test it by yourself with the attached program.
The issued reased up because of AMQ-3644, but it is actually a derby problem so
I post the issue here as well.
Derby writes multiple gigabyte of temporary files in its tmp directory during
one select statement. Afterwards these temporary files are deleted and rebuild
by the next Statement.
You can find a Test-Program (import it as a Maven-Eclipse project) which
reproduces this issue.
This program creates a derby database with a the activemq Message table and
fills it with data (2000 Messages, this can take several hours). I assumed 3MB
for one message as our messages contain same binary data and has an average
size of 3MB.
After the database is built one time a Statement and one time a
PreparedStatment is used to retrieve the next messages.
The Statement takes about 1 ms and the PreparedStatement about 258805 ms. Also
the second PreparedStatement takes as much time.
> Execution Time with a Statement 1 ms and with a PreparedStatement about 4
> minutes
> ---------------------------------------------------------------------------------
>
> Key: DERBY-5555
> URL: https://issues.apache.org/jira/browse/DERBY-5555
> Project: Derby
> Issue Type: Bug
> Reporter: Steffen Kuche
> Attachments: test.zip
>
>
> Sounds incrediable? Test it by yourself with the attached program.
> The issued reased up because of AMQ-3644, but it is actually a derby problem
> so I post the issue here as well.
> Derby writes multiple gigabyte of temporary files in its tmp directory during
> one select statement. Afterwards these temporary files are deleted and
> rebuild by the next Statement.
> You can find a Test-Program (import it as a Maven-Eclipse project) which
> reproduces this issue.
> This program creates a derby database with the activemq Message table and
> fills it with data (2000 Messages, this can take several hours). I assumed
> 3MB for one message as our messages contain same binary data and has an
> average size of 3MB.
> After the database is built one time a Statement and another time a
> PreparedStatment is used to retrieve the next messages.
> The Statement takes about 1 ms and the PreparedStatement about 258805 ms.
> Also the second PreparedStatement takes as much time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
