Timeline for Ways of visualizing event data in search of performance issues
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2012 at 21:14 | comment | added | Mike Dunlavey | @Geof: Good luck with visualization. The only tool I would have found useful is something to collect and merge the event logs so I could follow the path of one or more requests as it made its way through the various threads, 'cause that's the only way I know of to detect unnecessary delays. That's what any performance problem will consists of - unnecessary delays. | |
| Sep 12, 2012 at 18:59 | comment | added | Geoffrey Irving | In other words, there is no useful visualization of the data I have. :) Jed Brown suggested Jumpshot (and associated utilities) as one way to collect and visualize the data you suggest, so I'll look into that. | |
| Sep 12, 2012 at 12:59 | history | answered | Mike Dunlavey | CC BY-SA 3.0 |