Optimize tokio Runtime usage in benchmarks

[ixand]

Summary

This PR optimizes the usage of tokio::Runtime in benchmark files by instantiating it only once and passing it into benchmark functions, instead of creating it for every test case.

Why

• Reduces overhead of runtime creation
• Improves consistency and maintainability
• Cleaner code

Let me know if you'd prefer a different structure!

[codspeed-hq]

CodSpeed Performance Report

Merging #15 will not alter performance

_{Comparing ixand:optimize-runtime-in-bench (60696f5) with main (5282e85)}

Summary

✅ 17 untouched benchmarks
🆕 6 new benchmarks
⁉️ 6 dropped benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⁉️	organize_by_type[1000]	7 ms	N/A	N/A
⁉️	organize_by_type[100]	736.4 µs	N/A	N/A
⁉️	organize_by_type[500]	3.5 ms	N/A	N/A
⁉️	organize_modes[monthly]	8.6 ms	N/A	N/A
⁉️	organize_modes[type]	6.6 ms	N/A	N/A
⁉️	organize_modes[yearly]	7.8 ms	N/A	N/A
🆕	files[1000]	N/A	7 ms	N/A
🆕	files[100]	N/A	745.4 µs	N/A
🆕	files[500]	N/A	3.5 ms	N/A
🆕	mode[monthly]	N/A	8.8 ms	N/A
🆕	mode[type]	N/A	6.7 ms	N/A
🆕	mode[yearly]	N/A	7.7 ms	N/A

[mikeleppane]

Thanks for the contribution! 🙏
Please run cargo format and cargo clippy. You can use just format and just clippy for these. Make sure you have just installed: https://just.systems/man/en/packages.html

[ixand]

I am glad to contribute! So in the last commit I did what you asked me before and changed my approach to deal with it. I hope it will be useful!

…

On Tue, Jul 29, 2025 at 2:48 PM Mikko Leppänen ***@***.***> wrote: *mikeleppane* left a comment (mikeleppane/visualvault#15) <#15 (comment)> Thanks for the contribution! 🙏 Please run cargo format and cargo clippy. You can use just format and just clippy for these. Make sure you have just installed: https://just.systems/man/en/packages.html — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHUXZXPORRK57TZ3AOUZQEL3K5NPFAVCNFSM6AAAAACCS6MRLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZSGEYDKMBSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>