Skip to content

Getting Started

The published benchmark records one high-load test at 5,000 requests per second (RPS) on two AWS EC2 instance types. It is evidence for those test conditions, not a production capacity guarantee.

Observed highlights:

  • Success Rate: 100% in the recorded 5,000-RPS runs
  • Gateway overhead: 59µs on t3.medium and 11µs on t3.xlarge under the documented measurement method
  • Resource use: recorded throughput and memory stayed within each instance during the test window

DeepIntShield was benchmarked on two primary AWS EC2 instance configurations:

  • Buffer Size: 15,000
  • Initial Pool Size: 10,000
  • Use Case: Cost-effective option for moderate workloads
  • Buffer Size: 20,000
  • Initial Pool Size: 15,000
  • Use Case: High-performance option for demanding workloads

Metrict3.mediumt3.xlargeImprovement
Success Rate @ 5k RPS100%100%No failed requests
DeepIntShield Overhead59 µs11 µs-81%
Average Latency2.12s1.61s-24%
Peak Memory Usage1,312.79 MB3,340.44 MB+155%

Note: t3.xlarge tests used significantly larger response payloads (~10 KB vs ~1 KB), yet still achieved better performance metrics.


One of DeepIntShield’s key strengths is its configuration flexibility. You can fine-tune the speed ↔ memory trade-off based on your specific requirements:

Configuration ParameterEffect
initial_pool_sizeHigher values = faster performance, more memory usage
buffer_size & concurrencyControls queue depth and max parallel workers (per provider)
retry & timeoutTune aggressiveness for each provider to meet your SLOs

Configuration Philosophy:

  • Higher settings (like t3.xlarge profile) prioritize raw speed
  • Lower settings (like t3.medium profile) optimize for memory efficiency
  • Custom tuning lets you find the sweet spot for your specific workload

Ready to dive deeper? Choose your instance type above or learn how to run your own performance tests.