The test tool that we are using for the performance testing consumes more memory than the OpenDaylight controller. The goal of this task is to identify the source of the problem.

The most resource-consuming scenarios are executed with the following parameters:

NORTH
------------
java -Xmx27G -XX:MaxPermSize=256M -jar stress-client-1.10.0-SNAPSHOT-stress-client.jar --ip 127.0.0.1 --port 2830 --edits 16000 --exi false --ssh true --username admin --password admin --thread-amount 16 --async true --edit-batch-size 16000 --edit-content edit-l2fib-100.txt

SOUTH
-------------
java -jar netconf-testtool-1.10.0-SNAPSHOT-executable.jar --schemas-dir ./xrSchemas/ --ssh true --exi false --notification-file ./i2rs-notifs-perf100k10prefixes.xml --md-sal false --initial-config-xml-file initial-config.xml --thread-amount 1 --auth admin admin

E2E
--------------
java -Djava.security.egd=file:/dev/./urandom -Xmx27G -jar netconf-testtool-1.10.0-SNAPSHOT-executable.jar --ssh true --exi false --controller-destination localhost:8181 --generate-configs-batch-size 1 --schemas-dir ./xrSchemas/ --md-sal true --auth admin admin --device-count 64
java -Xmx15G -jar rest-perf-client-1.10.0-SNAPSHOT-rest-perf-client.jar --ip localhost --port 8181 --destination /restconf/operations/ncmount:write-routes --edits 320000 --edit-content json_routes_50.json --async-requests true --throttle 1000 --auth admin admin --thread-amount 64 --same-device false --timeout 30