Performance Benchmarks & Technical Metrics

Core Configuration Parameters

System default configuration, adjustable per actual requirements

12

Thread pool max concurrency

Server version default

Configurable

1GB

Desktop / standalone version file limit

Subscription / Server version

Configurable

10GB

Network version file limit

Network version default

Configurable

100/60s

Default rate limit

Configurable

3-10

K8s HPA replica count

Supports auto-scaling

9

Docker Compose service count

Database · Cache · API · Monitoring · Frontend, etc.

2

Task queue count

Compression task · Maintenance task

15

Compression scenario count

Covers mainstream application scenarios

Performance design goals for core security verification

<1ms

Authentication latency

Desktop / Mobile

<5ms

Authorization verification latency

Server-side

System default configuration parameters

Parameter	Default Value
Server version thread pool	12 concurrent
Standalone version file limit	1GB
Network version file limit	10GB
Default rate limit	100 times / 60 seconds
K8s HPA auto-scaling	3 ~ 10 replicas
Docker Compose services	9

Recommended steps to verify actual performance

Prepare test set: Select representative file samples (e.g., 10 photos of different resolutions, 5 PDFs of different sizes, 3 videos of different durations) covering your main usage formats.
Record original size: Record the original byte count of each file as the basis for compression ratio calculation.
Execute compression: Use the desktop version or call the SDK/API to perform compression, select the target compression level and scenario, and record compression time (using the time command or in-code timing).
Calculate compression ratio: Compression ratio = (original size - compressed size) / original size × 100%. It is recommended to aggregate statistics by format rather than mixing them together.
Quality assessment: For images/videos, compare PSNR or SSIM metrics to assess quality loss; for documents, manually check whether key content is clearly readable.
Concurrent testing (Server version): Use stress testing tools to send concurrent requests to the API and observe thread pool utilization and response latency.

Contact us to test against your actual file scenarios

Contact Us Get SDK for Self-Testing