encryption - Encrypted Vs Unencrypted EBS Volumes AWS -

encryption - Encrypted Vs Unencrypted EBS Volumes AWS -

we testing standard ebs volume, ebs volume encryption on ebs optimized m3.xlarge ec2 instance.

while analyzing test results, came know that

ebs volume encryption taking lesser time during read, write, read/write operations compared ebs without encryption. think there effect of latency on encrypted ebs volume because of encryption overhead on every i/o request.

what appropriate reason why ebs encrypted volumes faster normal ebs volumes??

expected results should ebs should yield improve results encrypted eebs.

results :

encrpted ebs results:

sysbench 0.4.12: multi-threaded scheme evaluation benchmark running test next options: number of threads: 8 initializing random number generator timer. file open flags: 16384 8 files, 512mb each 4gb total file size block size 16kb calling fsync() @ end of test, enabled. using synchronous i/o mode doing sequential write (creation) test threads started! done. operations performed: 0 read, 262144 write, 8 other = 262152 total read 0b written 4gb total transferred 4gb (11.018mb/sec) 705.12 requests/sec executed test execution summary: total time: 371.7713s total number of events: 262144 total time taken event execution: 2973.6874 per-request statistics: min: 1.06ms avg: 11.34ms max: 3461.45ms approx. 95 percentile: 1.72ms

ebs results:

sysbench 0.4.12: multi-threaded scheme evaluation benchmark running test next options: number of threads: 8 initializing random number generator timer. file open flags: 16384 8 files, 512mb each 4gb total file size block size 16kb calling fsync() @ end of test, enabled. using synchronous i/o mode doing sequential write (creation) test threads started! done. operations performed: 0 read, 262144 write, 8 other = 262152 total read 0b written 4gb total transferred 4gb (6.3501mb/sec) 406.41 requests/sec executed test execution summary: total time: 645.0251s total number of events: 262144 total time taken event execution: 5159.7466 per-request statistics: min: 0.88ms avg: 19.68ms max: 5700.71ms approx. 95 percentile: 6.31ms

please help me resolve issue.

that's unexpected conceptually , confirmed amazon ebs encryption:

[...] , you can expect same provisioned iops performance on encrypted volumes unencrypted volumes minimal effect on latency. can access encrypted amazon ebs volumes same way access existing volumes; encryption , decryption handled transparently , require no additional action you, ec2 instance, or application. [...] [emphasis mine]

amazon ebs volume performance provides more details on ebs performance in general - angle, pure speculation, maybe utilize of encryption implies default pre-warming amazon ebs volumes:

when create new ebs volume (general purpose (ssd), provisioned iops (ssd), or magnetic) or restore volume snapshot, back-end storage blocks allocated immediately. however, first time access block of storage, must either wiped clean (for new volumes) or instantiated snapshot (for restored volumes) before can access block. preliminary action takes time , can cause 5 50 percent loss of iops volume first time each block accessed. [...]

either way, suggest rerun benchmark after pre-warming both new ebs volumes, in case haven't done already.

encryption amazon-web-services amazon-ec2