[ 
https://issues.apache.org/jira/browse/DERBY-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xavion updated DERBY-6841:
--------------------------
    Attachment: 10.12.1.1-Fresh.txt
                10.12.1.1-Hard.txt
                10.12.1.1-Soft.txt
                10.11.1.1.txt

It looks like you've hit the nail on the head there: hard-upgrading the 
databases to v10.12.1.1 solved the problem.  I'm surprised that the massive 
performance difference caused by soft-upgrading hasn't been spotted by someone 
previously.  Ironically, the problem wouldn't have impacted me much anyway.  My 
databases are automatically regenerated on a weekly basis by whatever Derby 
version is installed at the time :-).

I've attached the results of the latest round of tests.  The filenames are 
fairly self-explanatory, but I'll quickly outline their meanings anyway:
* 10.11.1.1.txt: The tests were run on v10.11.1.1 databases using v10.11.1.1.
* 10.12.1.1-Soft.txt: The tests were run on v10.11.1.1 databases using 
v10.12.1.1 via soft-upgrading.
* 10.12.1.1-Hard.txt: The tests were run on (previously) v10.11.1.1 databases 
using v10.12.1.1 after hard-upgrading.
* 10.12.1.1-Fresh.txt: The tests were run on (new) v10.12.1.1 databases using 
v10.12.1.1.

> Derby v10.12.1.1 is horribly slow compared to v10.11.1.1 in embedded mode
> -------------------------------------------------------------------------
>
>                 Key: DERBY-6841
>                 URL: https://issues.apache.org/jira/browse/DERBY-6841
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, SQL
>    Affects Versions: 10.12.1.1
>         Environment: OS: Windows, OS X, Linux
> CPU: Quad-Core Intel i5
> App: Swing, multi-threaded
>            Reporter: Xavion
>             Fix For: 10.11.1.1
>
>         Attachments: 10.11.1.1.txt, 10.12.1.1-Fresh.txt, 10.12.1.1-Hard.txt, 
> 10.12.1.1-Soft.txt, DERBY_6841.java
>
>
> It takes much longer to open, read, and close embedded databases using 
> v10.12.1.1 than it did with v10.11.1.1.  What ever changes you guys made over 
> the last year and a bit have definitely been for the worse.
> Below are the results of the repetition tests I've just run on the same 
> computer with the same databases.  Let me know if you need to know about the 
> sizes of the databases and/or the file type they contain.
> Connecting with v10.11.1.1:
> Database opened in 0.82 seconds.
> Database opened in 0.77 seconds.
> Database opened in 0.88 seconds.
> Database opened in 0.77 seconds.
> Database opened in 0.77 seconds.
> Database opened in 0.96 seconds.
> Database opened in 0.74 seconds.
> Connecting with v10.12.1.1:
> Database opened in 1.98 seconds.
> Database opened in 2.07 seconds.
> Database opened in 1.97 seconds.
> Database opened in 2.01 seconds.
> Database opened in 2.01 seconds.
> Database opened in 2.00 seconds.
> Database opened in 2.03 seconds.
> Reading with v10.11.1.1:
> Database processed in 6.17 seconds.
> Database processed in 4.00 seconds.
> Database processed in 3.67 seconds.
> Database processed in 3.66 seconds.
> Database processed in 3.78 seconds.
> Database processed in 3.69 seconds.
> Database processed in 3.74 seconds.
> Reading with v10.12.1.1:
> Database processed in 7.29 seconds.
> Database processed in 4.54 seconds.
> Database processed in 4.88 seconds.
> Database processed in 4.65 seconds.
> Database processed in 4.34 seconds.
> Database processed in 4.35 seconds.
> Database processed in 4.50 seconds.
> Disconnecting with v10.11.1.1:
> Database closed in 0.11 seconds.
> Database closed in 0.13 seconds.
> Database closed in 0.15 seconds.
> Database closed in 0.14 seconds.
> Database closed in 0.10 seconds.
> Database closed in 0.13 seconds.
> Database closed in 0.14 seconds.
> Disconnecting with v10.12.1.1:
> Database closed in 0.74 seconds.
> Database closed in 0.87 seconds.
> Database closed in 0.76 seconds.
> Database closed in 0.87 seconds.
> Database closed in 0.85 seconds.
> Database closed in 0.69 seconds.
> Database closed in 0.84 seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to