db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5503) Measure the performance degradation incurred by encrypting Derby databases
Date Mon, 14 Nov 2011 23:46:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150089#comment-13150089
] 

Rick Hillegas commented on DERBY-5503:
--------------------------------------

I ran the single record update test to get some sense of the performance loss incurred by
Derby encryption. Here are the average transactions/second I saw on my machine using various
configurations:

No encryption: 898 tx/s

Default encryption: 874 tx/s (~ 3% performance loss)

AES 256-bit encryption: 788 tx/s (~ 12% performance loss)

Here is more information on the experiments I ran. I would appreciate advice about other experiments
which I should run to get a handle on this question. Thanks.

--------- NO ENCRYPTION -------

I ran the following experiment 10 times:

rm -rf db
java org.apache.derbyTesting.perf.clients.Runner \
    -driver org.apache.derby.jdbc.EmbeddedDriver \
    -url "jdbc:derby:db;create=true" \
    -init \
    -load sr_update \
    -threads 1 \ 

This yielded the following figures for transactions/seconds:

941, 795, 913, 863, 922, 942, 905, 927, 875, 893

--------- DEFAULT ENCRYPTION -------

I ran the following experiment 10 times:

rm -rf db
java org.apache.derbyTesting.perf.clients.Runner \
    -driver org.apache.derby.jdbc.EmbeddedDriver \
    -url "jdbc:derby:db;create=true;dataEncryption=true;encryptionKey=1234567890abcdef1234567890abcdef"
\
    -init \
    -load sr_update \
    -threads 1 \ 

This yielded the following figures for transactions/seconds:

903, 928, 881, 881, 814, 792, 894, 909, 868, 873

--------- AES 256-BIT ENCRYPTION -------

I ran the following experiment 10 times:

rm -rf db
java org.apache.derbyTesting.perf.clients.Runner \
    -driver org.apache.derby.jdbc.EmbeddedDriver \
    -url "jdbc:derby:db;create=true;dataEncryption=true;encryptionKeyLength=256;encryptionAlgorithm=AES/CBC/NoPadding;encryptionKey=1234567890abcdef1234567890abcdef"
\
    -init \
    -load sr_update \
    -threads 1 \ 

This yielded the following figures for transactions/seconds:

819, 778, 821, 809, 760, 733, 834, 772, 791, 759

                
> Measure the performance degradation incurred by encrypting Derby databases
> --------------------------------------------------------------------------
>
>                 Key: DERBY-5503
>                 URL: https://issues.apache.org/jira/browse/DERBY-5503
>             Project: Derby
>          Issue Type: Task
>          Components: Store
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>
> It would be good to measure the performance degradation incurred by Derby's encryption.

--
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

        

Mime
View raw message