Feature request: Add an option for Benchmarker to yield every X seconds, i.e. 0.1 or so, during benchmarking. This would allow me to run benchmarks for many minutes while I work on other things. Having it enabled could also add a Cancel button to the “Running benchmark…” screen.
Enable numbers of calls larger than 10k, but only when the yield option is enabled.
It would also give a bit more varied results when the functions being benchmarked include wildcards like Instance.new (which many of your library benchmarks do use, which is kind of a bad practice but whatever), although that’s not always desirable, hence the optionality.
I really want to buy this plugin, but I didn’t before because via robux it was like really expensive and just wasn’t worth it for the shares that Roblox would get, but, now I’ve noticed it moved to a real purchase thing, but now I can’t buy it, because, itch will not use the debit function (and might not be able to do so as I’m not on the USA), and I can’t use credit or use PayPal (as I’m -18), my bank does have an option for buying things with credit but working just like debit, but it won’t work for international purchases, so it doesn’t work either. Do you know like any other method that I could use to purchase Benchmarker? (apart from Robux which isn’t even a thing right now)
Didn’t mention in the patch notes cuz it was minor but the new + button inserts a barebones one, and the beginner template can be accessed from the library for those who need the aid.
Unsure if this is due to light theme, but the ModuleScript icon displayed is the default one, despite me using Elttob’s Vanilla theme.
ModuleScripts in the explorer are displayed correctly.
I don’t set the image myself, that’s the studio service returning the wrong class icon. Not sure how or why, but if you can find a repro go ahead and file a bug report.
Hello, i have some issue with optimizing script where i got some memories leak, microprofiler is kinda hard to use and i was wondering if this plugin could help to understand and find issue in code easly or is this usefull for other type of problems, Thanks !
After buying the plugin I have to say that I’m disappointed.
There are so many bugs and fixing them was nothing less than hell — the code is extremely unoptimized and unreadable, and the coding style isn’t even consistent.
It’s almost impossible to fix bugs or add new features like I’ve done, simply due to the awful source code. The big issue being that I have to fix bugs for it to even be usable.
The biggest bug is that the flamechart doesn’t even resemble the fiftieth values, only displays them. I’m not quite sure what it actually measures. I’ve attempted to fix it, but to no avail. I can’t publish incorrect graphs for my libraries’ performance, so this is a “game-breaking” bug, because it makes the plugin basically unusable.
I know this is a very old resource, that hasn’t been updated in a while, but that doesn’t really make the issues non-existent. I really hope this gets adressed.
You can report any bugs you encounter. You haven’t provided any examples or specifics, so no one can help you resolve any issues. What problems are you running into?
This is not a bug at all, this is called Separation of Concerns. A UI component should only be concerned with displaying data, not computing it.
Please provide examples of incorrect graphs and reproduction steps so that they can be fixed.
Version 7.3.0 came out only four months ago, this plugin is definitely maintained.
I’m sorry to hear you’ve been frustrated with this plugin, but if you want it to improve then you’ll need to provide more information.
Huge letdown
