-
Notifications
You must be signed in to change notification settings - Fork 28
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
Call for beta testing! #63
Comments
thanks! @Lectem maybe interesting for you too ? |
I'll take a look tomorrow. Thanks for posting! |
I'll look into it asap. Thanks for your efforts!
…On Wed, Jan 6, 2021 at 10:14 PM Tomas Dittmann ***@***.***> wrote:
I'll take a look tomorrow. Thanks for posting!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADTBHL3YS7TNLZRJR4TFL6TSYTHELANCNFSM4VYATCFQ>
.
|
I'm sorry to say this @jcelerier and be a bit blunt, but I'm not really a fan of anything based on auto-instrumentation. It can be useful to know what functions are called most but other than that it's just not great for profiling (especially when it prevents any inlining) and prefer manual instrumentation coupled with sampling. Anyway a few remarks for @tyoma for the UI since I tried it anyway:
On other issues:
|
Thank you @Lectem! This is very valuable!
As a sidenote: I get what you're saying about inlining - it may reduces the amount of functions inlined, but not prevent it. You can check it out yourself here - I ran profiling of the same agge rendition code with and without inlining (in Release, all other optimizations and flags are the same). You can look at the spreadsheet or at the profiles attached (you can open them from the Extensions/MicroProfiler/Open...) agge-rendition-with-or-without-inlining.zip |
- implements one of the requests in Issue #63 (#63 (comment)).
See the space between the pie chart and the first column Rest of the answer moved to #64 |
moved to #64 (comment) |
Moved to #64 (comment) |
@Lectem I've published a version with some of the issues you mentioned earlier fixed. Here it is: https://github.com/tyoma/micro-profiler/releases/tag/v1.8.626.0 |
Guys,
You're on this list because you were/are at some point interested in MicroProfiler and left an issue or two here on github.
I have released a beta that has entirely rebuilt UI (particularly, the lists are now drawn by my code - except for parsing fonts, for which I use freetype2 library). Since there nobody else's helping me in developing MicroProfiler, I need your help in testing this release.
Should you decide to participate, the release is located here. Please, feel free open new issues here.
Have fun tackling it and Happy New Year!
Thanks a bunch!
Artem
@sebhtml, @pk1954, @SergeLalonde, @voidmonoid, @boimart1, @klukander, @srogatch, @janhec, @rold2007, @icnocop, @7wgs0gr04v, @denis-bu, @jpouderoux, @jcelerier, @Chaosmeister, @OlegRa
The text was updated successfully, but these errors were encountered: