-
Notifications
You must be signed in to change notification settings - Fork 16
java benchmark #1985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
java benchmark #1985
Changes from all commits
16ba590
3603352
5ff2834
50fffe6
9a7d2a8
6d28b94
e81fa5a
d452ac7
32d09c8
57d63ac
c4961db
2addae7
3e82ca0
bf559b7
e2a5e14
dbcf6ff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# DB-ESDK Performance Test Scenarios Configuration | ||
|
||
# Data sizes to test (in bytes) | ||
# Categories are for organization only - code processes all sizes regardless of category | ||
data_sizes: | ||
small: | ||
- 1024 # 1KB | ||
- 5120 # 5KB | ||
- 10240 # 10KB | ||
medium: | ||
- 102400 # 100KB | ||
- 512000 # 500KB | ||
- 1048576 # 1MB | ||
- 10000000 # 10 MB | ||
large: | ||
- 10485760 # 10MB | ||
- 52428800 # 50MB | ||
- 100000000 | ||
- 104857600 # 100MB | ||
|
||
# Quick test configuration (reduced test set for faster execution) | ||
quick_config: | ||
data_sizes: | ||
small: | ||
- 102400 # 100KB - within DynamoDB's 400KB limit | ||
iterations: | ||
warmup: 3 # Reduced warmup iterations | ||
measurement: 3 # Reduced measurement iterations | ||
concurrency_levels: | ||
- 1 | ||
- 2 | ||
test_types: | ||
- "throughput" | ||
- "memory" | ||
- "concurrency" | ||
|
||
# Test iterations for statistical significance | ||
iterations: | ||
warmup: 5 # Warmup iterations (not counted) | ||
measurement: 10 # Measurement iterations | ||
|
||
# Concurrency levels to test | ||
concurrency_levels: | ||
- 1 | ||
- 2 | ||
- 4 | ||
- 8 | ||
- 16 | ||
|
||
# DynamoDB table name | ||
table_name: "dbesdk-performance-testing" | ||
|
||
# Keyring | ||
keyring: "raw-aes" |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,190 @@ | ||
# DB-ESDK Performance Benchmark - Java | ||
|
||
This directory contains the Java implementation of the AWS Database Encryption SDK (DB-ESDK) performance benchmark suite. | ||
|
||
## Overview | ||
|
||
The Java benchmark provides comprehensive performance testing for the DB-ESDK Java runtime, measuring: | ||
|
||
- **Throughput**: Operations per second and bytes per second using DynamoDB batch operations | ||
- **Latency**: Put, get, and end-to-end timing for encrypted DynamoDB operations | ||
- **Memory Usage**: Peak memory consumption and efficiency | ||
- **Concurrency**: Multi-threaded performance scaling | ||
- **Statistical Analysis**: P50, P95, P99 latency percentiles | ||
|
||
## Prerequisites | ||
|
||
- Java 17 or higher | ||
- Maven 3.6 or higher | ||
- Local DynamoDB instance running on localhost:8000 | ||
- Access to AWS Database Encryption SDK for DynamoDB Java libraries | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: This wording is very odd. |
||
|
||
## Local DynamoDB Setup | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Issue: I do not think Local DynamoDB is required. |
||
|
||
Start a local DynamoDB instance: | ||
|
||
```bash | ||
# Using Docker | ||
docker run -p 8000:8000 amazon/dynamodb-local | ||
|
||
# Or download and run DynamoDB Local | ||
java -Djava.library.path=./DynamoDBLocal_lib -jar DynamoDBLocal.jar -sharedDb -port 8000 | ||
``` | ||
|
||
Create the test table: | ||
|
||
```bash | ||
aws dynamodb create-table \ | ||
--table-name db-esdk-performance-test \ | ||
--attribute-definitions \ | ||
AttributeName=partition_key,AttributeType=S \ | ||
AttributeName=sort_key,AttributeType=N \ | ||
--key-schema \ | ||
AttributeName=partition_key,KeyType=HASH \ | ||
AttributeName=sort_key,KeyType=RANGE \ | ||
--billing-mode PAY_PER_REQUEST \ | ||
--endpoint-url http://localhost:8000 | ||
Comment on lines
+34
to
+46
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Issue: I do not think this DDB table is required. |
||
``` | ||
|
||
## Building | ||
|
||
```bash | ||
# Build the project | ||
mvn clean compile | ||
|
||
# Create executable JAR | ||
mvn clean package | ||
|
||
# Run tests | ||
mvn test | ||
``` | ||
|
||
## Running Benchmarks | ||
|
||
### Quick Test | ||
|
||
```bash | ||
# Using Maven | ||
mvn exec:java -Dexec.mainClass="com.amazon.esdk.benchmark.Program" -Dexec.args="--quick" | ||
|
||
# Using JAR | ||
java -jar target/esdk-benchmark.jar --quick | ||
``` | ||
|
||
### Full Benchmark Suite | ||
|
||
```bash | ||
# Using Maven | ||
mvn exec:java -Dexec.mainClass="com.amazon.esdk.benchmark.Program" | ||
|
||
# Using JAR | ||
java -jar target/esdk-benchmark.jar | ||
``` | ||
|
||
### Custom Configuration | ||
|
||
```bash | ||
# Specify custom config and output paths | ||
java -jar target/esdk-benchmark.jar \ | ||
--config /path/to/config.yaml \ | ||
--output /path/to/results.json | ||
``` | ||
|
||
## Command Line Options | ||
|
||
- `--config, -c`: Path to test configuration file (default: `../../config/test-scenarios.yaml`) | ||
- `--output, -o`: Path to output results file (default: `../../results/raw-data/java_results.json`) | ||
- `--quick, -q`: Run quick test with reduced iterations | ||
- `--help, -h`: Show help message | ||
|
||
## Configuration | ||
|
||
The benchmark uses a YAML configuration file to define test parameters: | ||
|
||
```yaml | ||
data_sizes: | ||
small: [1024, 5120, 10240] | ||
medium: [102400, 512000, 1048576] | ||
large: [10485760, 52428800, 104857600] | ||
|
||
iterations: | ||
warmup: 5 | ||
measurement: 10 | ||
|
||
concurrency_levels: [1, 2, 4, 8] | ||
``` | ||
|
||
## Output Format | ||
|
||
Results are saved in JSON format with the following structure: | ||
|
||
```json | ||
{ | ||
"metadata": { | ||
"language": "java", | ||
"timestamp": "2025-09-05T15:30:00Z", | ||
"javaVersion": "17.0.2", | ||
"cpuCount": 8, | ||
"totalMemoryGB": 16.0, | ||
"totalTests": 45 | ||
}, | ||
"results": [ | ||
{ | ||
"test_name": "throughput", | ||
"language": "java", | ||
"data_size": 1024, | ||
"concurrency": 1, | ||
"put_latency_ms": 0.85, | ||
"get_latency_ms": 0.72, | ||
"end_to_end_latency_ms": 1.57, | ||
"ops_per_second": 636.94, | ||
"bytes_per_second": 652224.0, | ||
"peak_memory_mb": 0.0, | ||
"memory_efficiency_ratio": 0.0, | ||
"p50_latency": 1.55, | ||
"p95_latency": 1.89, | ||
"p99_latency": 2.12, | ||
"timestamp": "2025-09-05T15:30:15Z", | ||
"java_version": "17.0.2", | ||
"cpu_count": 8, | ||
"total_memory_gb": 16.0 | ||
} | ||
] | ||
} | ||
``` | ||
|
||
## Key Features | ||
|
||
### DB-ESDK Integration | ||
- Uses AWS Database Encryption SDK for DynamoDB with transparent encryption | ||
- Configures attribute actions (ENCRYPT_AND_SIGN, SIGN_ONLY, DO_NOTHING) | ||
- Tests actual DynamoDB operations with client-side encryption | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Issue: I did not see any actual DDB operations, just the Item Encryptor. |
||
- Uses Raw AES keyring for consistent performance testing | ||
|
||
### Batch Operations | ||
- Performs BatchWriteItem operations with 25 items per batch | ||
- Measures BatchGetItem operations with consistent reads | ||
- Tests realistic DynamoDB workloads with encryption overhead | ||
Comment on lines
+164
to
+167
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Issue: I did not see any DDB Batch operations... is the AI going wild? |
||
|
||
### Performance Metrics | ||
- **Throughput Tests**: Measures ops/sec and bytes/sec for batch operations | ||
- **Memory Tests**: Tracks peak memory usage during encrypted operations | ||
- **Concurrency Tests**: Evaluates multi-threaded performance scaling | ||
- **Latency Analysis**: P50, P95, P99 percentiles for operation timing | ||
|
||
## Dependencies | ||
|
||
Key dependencies used in this benchmark: | ||
|
||
- **AWS Database Encryption SDK for DynamoDB**: Core encryption functionality for DynamoDB | ||
- **AWS Cryptographic Material Providers**: Keyring and cryptographic material management | ||
- **AWS SDK for Java v2 DynamoDB**: DynamoDB client operations | ||
- **Jackson**: JSON/YAML processing | ||
- **Commons CLI**: Command line argument parsing | ||
- **ProgressBar**: Visual progress indication | ||
- **SLF4J**: Logging framework | ||
- **JUnit**: Unit testing (test scope) | ||
|
||
## License | ||
|
||
This benchmark suite is part of the AWS Encryption SDK project and follows the same licensing terms. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue: I do not think that Local DynamoDB is required.