Performance profiling » History » Version 1
Radhika Chippada, 05/05/2015 07:10 PM
| 1 | 1 | Radhika Chippada | h1. Performance profile workbench |
|---|---|---|---|
| 2 | |||
| 3 | |||
| 4 | h2. Problem |
||
| 5 | |||
| 6 | Workbench makes repeated calls for the same object(s) from the API server. Also, workbench sometimes makes multiple calls to the API server. For ex: get a link, one at a time rather than pulling all links needed by the object in one request from API server. This was observed several times in the past. And, we have used “preload-*” in those instances when we noticed this. |
||
| 7 | |||
| 8 | As recently as of fixing #5622, it was observed that each link was being retrieved in a separate call. Similar behavior is observed in #5908. |
||
| 9 | |||
| 10 | Given this, it is clear that we have this symptom in several areas in workbench. It is likely that we have other such problem patterns in our implementation. |
||
| 11 | |||
| 12 | Thus, it makes sense to do performance profiling of workbench to identify potential areas of improvement in workbench. This can also help identify API methods that can be tweaked to improve API server performance. |
||
| 13 | |||
| 14 | h2. Proposed solutions |
||
| 15 | |||
| 16 | h3. Profile using ruby-prof |
||
| 17 | |||
| 18 | This seems like a good profiling tool and we are already using it in our performance testing. |
||
| 19 | |||
| 20 | http://pivotallabs.com/rubyrails-performance-tools/ |