-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Add performance reports & comparisons to other major maven hosts #1137
Comments
I think that when we'll have stable 3.x we could invest some time to write benchmarks. A few notes to the proposed scenarios:
Also, you need 2 machines to perform reliable tests - for client & server. |
Still, that is a reason to take it into account. Performance benchmarks should be used to show users whether or not this tool is appropriate for them. So, being transparent that the other repository servers perform better with large quantities of ram and cache should be shown.
Yeah, ofc. I'm assuming it'd be done on a VPS with decent I/O speeds.
True, I just thought it would be good to use something that accurately models the real world.
It could also be 2 virtual machines containerized using something liker KVM. Also the different quantities of artifacts in the server has the goal of seeing how other maven repo servers compare when there are more/less artifacts |
I mean, the result might be different, because there is e.g. disk cache, but it'd be unrelated to Reposilite internals. Also, I've added it more like a note, because I assume most people don't know how Reposilite works under the hood, so it's good to mention it anyway. Speaking of preparing such benchmark, it should be:
I'd keep it simple, so we may start with only one mainstream manager:
And later we can extend it :) |
Of course. |
Results could be summarized in guide: |
Request Details
I found reposilite and am very interested in this project.
And although I don't doubt the claims that reposilite, I'd be interested to see how it compares in terms of performance to the other major players.
I believe the following measurements would be beneficial to record:
The following statistics should also be recorded for each test execution, so that the bottlenecks of each server can be observed:
The tests should also be run in the following environments:
(If you can't/don't want to run it in all those different environments because of money, it can always just be run with jvm args to limit mem usage, to simulate lower spec systems.)
The test would also be run with different amounts of artifacts:
To get such a large quantity of artifacts, a random selection of artifacts can be downloaded from maven central and be rehosted for the purpose of testing.
I would be more than happy to help with writing the programs to perform these tests, or any other ways I'd be able to contribute.
The text was updated successfully, but these errors were encountered: