You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the way stat works is quite different from things like Xdebug that just dump a valgrind blob that can be parsed after the fact, a short example could ease in developers who wish to try stat, but are used to valgrind tooling.
It would be helpful to have a small example of a stat client (even in pseudo-code) that displays how to aggregate and parse the frame data that the stat socket outputs, in order to see how a function or a class is performing.
Or is this on a roadmap, but is post-poned until stat is more developed in terms of features and polish?
The text was updated successfully, but these errors were encountered:
Right now, I'm focused on the internals of stat, the format of data over the wire and so on. It's quite fast moving and likely to change (#7).
In addition, I'm hoping that collaborators will come forward to help shape data and API ...
I think I'll aim to start writing some Wiki pages sometime soon, about the general differences between a conventional profiler and stat and the different applications the data might have (it's not restricted to a profiler).
I see, sounds like a solid plan. Let me know if you need help in validating Wiki contents when you begin working on them. I will try and see how a stat client could work and see if I can be of any help there if I have the time.
As the way stat works is quite different from things like Xdebug that just dump a valgrind blob that can be parsed after the fact, a short example could ease in developers who wish to try stat, but are used to valgrind tooling.
It would be helpful to have a small example of a stat client (even in pseudo-code) that displays how to aggregate and parse the frame data that the stat socket outputs, in order to see how a function or a class is performing.
Or is this on a roadmap, but is post-poned until stat is more developed in terms of features and polish?
The text was updated successfully, but these errors were encountered: