Use Virtual Threads

[mageddo]

What is expected

• Optimize resource utilization by using Java Virtual Threads

What is Happening

What is the actual behavior and lacks without this feature and what's the fallback while this feature is not implemented yet

Changes (Optional)

• [x] Migrate thread pools to virtual thread ExecutorService
• [x] Create stress-test module which will point to an running instance of DPS
• [x] Create way to collect metrics of a running instance of DPS to compare the resources utilized across different versions

Refs

Export a process stats to Prometheus

• process-exporter
• instrumenting exporters

How to export docker metrics (the docker engine itself not specific container metrics)

• monitor-infrastructure/integrations/integration-reference/integration-docker
• Collect Docker metrics with Prometheus
• How to monitor Docker metrics using Prometheus & Grafana?

Data

docker-compose -f src/stress-test/docker/docker-compose.yaml up  --build
rate(container_cpu_user_seconds_total[30s]) * 100
dig google.com @127.0.0.1 -p5753
https://stackoverflow.com/a/34930574/2979435

Depends on #435

[mageddo]

3.24.0 (No Virtual Threads)

 this.doNRequestsFor(executor, 1_000, Duration.ofSeconds(20));

Using Virtual Threads

 this.doNRequestsFor(executor, 1_000, Duration.ofSeconds(20));