Repository navigation
Export benchmarked data into json, csv #19
Description
Activity
This could be used as an extension to RubyMine that provides context-sensitive tips for better performance
- changed the title
[-]Export benchmarked data into json[/-][+]Export benchmarked data into json, csv[/+]on Feb 25, 2015 This could be used as an extension to RubyMine that provides context-sensitive tips for better performance
Nice! How do I create these tips for RubyMine?
So, I'm not sure what should be done here. Maybe we export this json with our test runs?
An alternative is to create a command that exports this data so that other libs can possibly call it.
Finally, this issue has been around for so long without conclusion that maybe it's not worth the trouble? At least for now. I like the motivation, which is why I think it'd be interesting to expose some sort of command that could just export all the benchmarks into a json file.
What do you think, @ashwinisukale?
@mateusdeap agree, idea is nice, need to check if we already have any export functionality and if we have then we can add one more option or command in it to get the data.
- Oke Pada tanggal Sel, 11 Okt 2022 15.48, Ashwini Sukale < ***@***.***> menulis:…@mateusdeap <https://github.com/mateusdeap> agree, idea is nice, need to check if we already have any export functionality and if we have then we can add one more option or command in it to get the data. — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3MSGSDVGCDBCJ6WZCMSG5DWCUSW7ANCNFSM4A3IDBXQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Every CI run now saves each benchmark's benchmark-ips report as JSON (#241), and the results site publishes all of them in one file, https://fastruby.github.io/fast-ruby/results.json, next to the page built from it, https://fastruby.github.io/fast-ruby/ (#250). There's no CSV, but the JSON has each report's i/s and error on every Ruby.
Closing.
Then we can leverage this json to create a web page to list common idioms's performance across many implementations.