https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-237 controller <p>Operating System: All<br/> Platform: All</p> CONTROLLER-237

Milestone: Analysis and fixing of performance & memory issues

Improvement Resolved Done Tony Tkacik Tomas Olvecky Thu, 27 Mar 2014 10:04:09 +0000 Tue, 25 Jul 2023 08:23:18 +0000 Mon, 29 Jun 2015 07:44:42 +0000 restconf Thu, 25 Jun 2015 00:00:00 +0000 0 6 <p>Please add a description of what is being asked. What is it that we want to performance test? How do we test restconf performance while seperating out performance issues in the broker / lower levels of MD-SAL?</p> <p>More details required, or please close this item as not needed.</p> <p>Performance today for GET and PUT requests is around 400 req/sec on a MACbookPro 2.2 Ghz Intel Core i7 with 8Gb RAM. </p> <p><a href="https://lists.opendaylight.org/pipermail/controller-dev/2014-June/005116.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/controller-dev/2014-June/005116.html</a></p> <p>Given performance number are closely related, it points to some common infrastructure limitation. </p> <p>The test does not manage to separate if bottleneck is in RESTconf or datastore, it is the performance of the entire code path.</p> <p>See this thread for reference</p> <p>Some investigation is needed to narrow down the bottleneck further.</p> Blocks CONTROLLER-1073 MDSAL-54 Development External issue ID 599 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02j5r: