[CONTROLLER-237] Milestone: Analysis and fixing of performance & memory issues Created: 27/Mar/14 Updated: 25/Jul/23 Due: 25/Jun/15 Resolved: 29/Jun/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Tomas Olvecky | Assignee: | Tony Tkacik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||
| Comments |
| Comment by Devin Avery [ 29/May/14 ] |
|
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? More details required, or please close this item as not needed. |
| Comment by Reinaldo Penno [ 24/Jun/14 ] |
|
Performance today for GET and PUT requests is around 400 req/sec on a MACbookPro 2.2 Ghz Intel Core i7 with 8Gb RAM. https://lists.opendaylight.org/pipermail/controller-dev/2014-June/005116.html Given performance number are closely related, it points to some common infrastructure limitation. The test does not manage to separate if bottleneck is in RESTconf or datastore, it is the performance of the entire code path. See this thread for reference Some investigation is needed to narrow down the bottleneck further. |