Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The current performance test of ACM-R is made by jmeter. The jmeter file is configured with a cycle where a composition in created and primed, and an instance is deployed, undeployed and deleted. The test is made again a Kubernetes environment defined in policy/docker.

We need to investigate the performance of ACM-R whit hundreds of compositions and instances deployed at same time and determine minimal/recommended requirements of memory and CPU.

Test using 100 compositions and instances

policy-clamp-runtime-acm

 Limits:
      cpu:     1
      memory:  4Gi
    Requests:
      cpu:        100m
      memory:     1Gi

system_cpu_usage

jvm_memory_used_bytes


http_server_requests_seconds_max


spring_data_repository_invocations_seconds_max





  • No labels