Confirmed users
32
edits
MemoryProfiler: Difference between revisions
Jump to navigation
Jump to search
features
m (→Objectives) |
(features) |
||
| Line 43: | Line 43: | ||
With the help of the timestamp, a size-time map can be plotted, too. | With the help of the timestamp, a size-time map can be plotted, too. | ||
== | == Features == | ||
The profiler is composed of two parts: the sampling engine and the front-end. Currently most of the efforts are devoted to the back-end and only a few JavaScript examples (quite useful but less convenient than you would expect) is available to give access to the profiler. | The profiler is composed of two parts: the sampling engine and the front-end. Currently most of the efforts are devoted to the back-end and only a few JavaScript examples (quite useful but less convenient than you would expect) is available to give access to the profiler. | ||
The profiler will be able to | |||
* Provide a way to start/stop | |||
* A timeline that: | |||
** shows the overall memory usage history | |||
** allows zooming into a time interval for the following views | |||
* A rank-list view that shows top functions that are most memory eager | |||
** 6 measurements: {retained, allocated, peak} x {self, inclusive} | |||
* A tree view that shows functions as call trees | |||
** 6 measurements: {retained, allocated, peak} x {self, inclusive} | |||
* A filter to focus on interested functions | |||