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

Very very nice😀 #10

Open
danp11 opened this issue Jan 17, 2025 · 1 comment
Open

Very very nice😀 #10

danp11 opened this issue Jan 17, 2025 · 1 comment

Comments

@danp11
Copy link

danp11 commented Jan 17, 2025

Hello @lampajr and @johnaohara .

The opposite to an issue😀 but I just wanted to say Thanks for the time you both have invested in this. It helps alot for a person like me that just started learning Hyperfoil/Horreum, to see a blue-print for how to organize/execute benchmarks.

If possible it would be fantastic if you also could add an example of how the testdata also could be sent to Horreum for further analysis.

Thanks for your work.

/Dan

@lampajr
Copy link
Member

lampajr commented Jan 20, 2025

Hi @danp11, I am really glad to hear that 😃

If possible it would be fantastic if you also could add an example of how the testdata also could be sent to Horreum for further analysis.

The idea is to send the run.json file that is generated by qDup and that contains whatever you want to save/extract during the run execution. There is still a bit of work to extract some metrics and export them as qDup states but we should be able to provide some examples of that (you should be even able to run it on your own and check the resulting run.json)

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

No branches or pull requests

2 participants