16758

Performance Analysis of CUDA and OpenCL By Implementation of Cryptographic Algorithms

Manas Mahapatra
Department of Computer Science and Engineering, National Institute of Technology Rourkela, Rourkela-769 008, Odisha, India
National Institute of Technology Rourkela, 2015

@phdthesis{mahapatra2015performance,

   title={Performance Analysis of CUDA and OpenCL by Implementation of Cryptographic Algorithms},

   author={Mahapatra, Manas},

   year={2015}

}

Download Download (PDF)   View View   Source Source   

1285

views

This paper presents a Performance Analysis of CUDA and OpenCL. Three different cryptographic algorithms, i.e. DES, MD5, and SHA-1 have been selected as the benchmarks for extensive analysis of the performance gaps between the two. Our results show that, on the average scenario, CUDA performs 27% better than OpenCL while in the best case scenario it takes over OpenCL by 30%.We also infer that CUDA is more stable and completely masks the access latencies to the shared memory due to the contention of 16 read ports. As far as the optimal number of threads per block goes, 256 threads per block is the most performant choice, proving that the CUDA architecture is able to deal with an increased pressure on the register file without problems as CUDA scores 4.5times over OpenCL in terms of stability.
VN:F [1.9.22_1171]
Rating: 3.0/5 (2 votes cast)
Performance Analysis of CUDA and OpenCL By Implementation of Cryptographic Algorithms, 3.0 out of 5 based on 2 ratings
  • Stefano B

    What kind of analisis is this?

    1) He used a Nvidia 525M that, from Nvidia site, does NOT support OpenCl 2.0 (in the pdf he said that he used OpenCl 2.0).
    2) I know Cuda doesn’t run on Amd/Intel gpus, but why not to try the same simulation on different platform with OpenCl to see behaviors?
    3) Why use an old mobile gpu (525M released January 2011) for benchmarks? He wrote the doc in May 2015 and he could use a more recent gpu.
    No sense…..

* * *

* * *

TwitterAPIExchange Object
(
    [oauth_access_token:TwitterAPIExchange:private] => 301967669-yDz6MrfyJFFsH1DVvrw5Xb9phx2d0DSOFuLehBGh
    [oauth_access_token_secret:TwitterAPIExchange:private] => o29ji3VLVmB6jASMqY8G7QZDCrdFmoTvCDNNUlb7s
    [consumer_key:TwitterAPIExchange:private] => TdQb63pho0ak9VevwMWpEgXAE
    [consumer_secret:TwitterAPIExchange:private] => Uq4rWz7nUnH1y6ab6uQ9xMk0KLcDrmckneEMdlq6G5E0jlQCFx
    [postfields:TwitterAPIExchange:private] => 
    [getfield:TwitterAPIExchange:private] => ?cursor=-1&screen_name=hgpu&skip_status=true&include_user_entities=false
    [oauth:protected] => Array
        (
            [oauth_consumer_key] => TdQb63pho0ak9VevwMWpEgXAE
            [oauth_nonce] => 1484853113
            [oauth_signature_method] => HMAC-SHA1
            [oauth_token] => 301967669-yDz6MrfyJFFsH1DVvrw5Xb9phx2d0DSOFuLehBGh
            [oauth_timestamp] => 1484853113
            [oauth_version] => 1.0
            [cursor] => -1
            [screen_name] => hgpu
            [skip_status] => true
            [include_user_entities] => false
            [oauth_signature] => 4R+Dt/K43ZBmoT7x7vxbT0i5UpU=
        )

    [url] => https://api.twitter.com/1.1/users/show.json
)
Follow us on Facebook
Follow us on Twitter

HGPU group

2134 peoples are following HGPU @twitter

HGPU group © 2010-2017 hgpu.org

All rights belong to the respective authors

Contact us: