Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling? #60

Open
eoliphan opened this issue Dec 1, 2022 · 5 comments
Open

Profiling? #60

eoliphan opened this issue Dec 1, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@eoliphan
Copy link

eoliphan commented Dec 1, 2022

Would it be possible (or even desirable) to add some sort of optional profiling? Obviously this wouldn't replace or be as accurate as dedicated tools like criterium, etc. But it would be nice to be able to see rough numbers, such that I make a tweak and i can see that some call went from X to 1/2 X.

P.S. FlowStorm is awesome!

@jpmonettas
Copy link
Member

hi @eoliphan! Thanks!

Sure, I have thought about it. Not sure it would make an accurate profiler but with very light instrumentation (just fn calls and returns) should be ok to measure how long fns take to execute I guess.

@jpmonettas jpmonettas added the enhancement New feature or request label Dec 1, 2022
@velios
Copy link
Contributor

velios commented Dec 18, 2023

@jpmonettas Was this idea realized? I actively use flowstorm, but I don’t know how to enable it, although it would be useful.

@jpmonettas
Copy link
Member

@velios there insn't anything for measuring performance implemented yet, but measuring pretty accurate results shouldn't be hard if we create a special "performance mode".

With this I mean that in "perf measuring mode" we can setup ClojureStorm callbacks to just trace fn-call and fn-return (and disable the rest) with callbacks that just store the timestamps for functions calls and functions returns in a specialized structure. Then maybe create a Performance tool tab with various ways of looking at this.

@velios
Copy link
Contributor

velios commented Dec 18, 2023

@jpmonettas This would be great, if of course you have time for it. Functionality of storm is breathtaking, but I'm sure it takes a lot of time to maintain. I'd like to contribute to project in the future, but project seem a pretty hard to understand, especially the part where the user interface interacts with the rest of the tool.

@jpmonettas
Copy link
Member

@velios I'll eventually work on this, but if you are interested in the project internals and contributing there is https://flow-storm.github.io/flow-storm-debugger/user_guide.html#_internals_diagrams_and_documentation which links to dev_notes, and a bunch of diagrams.

Also don't hesitate to ask in #flow-storm channel on the Clojurians Slack or DM me if you have any questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants