[aarch64-port-dev ] Some benchmarking help required

Andrew Haley aph at redhat.com
Wed May 16 17:03:16 UTC 2018


On 05/16/2018 03:48 PM, Dmitry Chuyko wrote:
> 
> On 05/16/2018 05:44 PM, Andrew Haley wrote:
>> On 05/16/2018 03:21 PM, Dmitry Chuyko wrote:
>>> I personally like the AES results on both machines! It looks like the
>>> first short patch makes the difference.
>> But that is really strange because we have AES hardware.  The C2
>> compiler should not affect anything.
> Yes. And both ones do have it.

Here's the answer, from a run of crypto.aes:

7464759  40.0675  16257.jo                 java                     void com.sun.crypto.provider.DESedeCrypt.decryptBlock(byte[], int, byte[], int)~1
7461795  40.0516  16257.jo                 java                     int com.sun.crypto.provider.CipherBlockChaining.implEncrypt(byte[], int, int, byte[], int)~2
991198    5.3203  16257.jo                 java                     void com.sun.crypto.provider.DESCrypt.perm(int, int, byte[], int)
787277    4.2258  16257.jo                 java                     void com.sun.crypto.provider.AESCrypt.implDecryptBlock(byte[], int, byte[], int)
735359    3.9471  16257.jo                 java                     void com.sun.crypto.provider.AESCrypt.implEncryptBlock(byte[], int, byte[], int)

Despite the name of the benchmark, it's doing a great deal of DES
encryption.  The time taken by the AES code is relatively tiny.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671


More information about the aarch64-port-dev mailing list