-
Notifications
You must be signed in to change notification settings - Fork 15
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
Benchmark S3 gateway #102
Comments
The benchmark https://github.com/chinglinwen/s3-benchmark works. Example how to execute: ./s3-benchmark -a %ACCESS_KEY_ID -s %SECRET_KEY -u %ENDPOINT Result: Wasabi benchmark program v2.0 |
The benchmark https://github.com/wasabi-tech/s3-benchmark doesn't work because of #119 |
Benchmark build:
Intended key setup and test run (new key for the gateway, standard dev env key for the client, it doesn't work):
Real key setup and test run (dev env key for the gateway):
|
During this #137 I found that Wasabi's benchmark uses Signature Version 2. Headers of requests which Wasabi benchmark creates, seems like the example of header here: This version is deprecated: The gateway receives headers of Signature Version 4: The fork of this benchmark -- https://github.com/chinglinwen/s3-benchmark -- uses the new version. What do you think, @realloc ? |
Also Wasabi's benchmark looks abandoned. |
One more option from @realloc: https://github.com/ceph/s3-tests |
For the benchmark, let's fork wasabi and make all the small changes we need to make it work with our system. We need the benchmark to compare the S3 Protocol Gateway performance against plain NeoFS gRPC API, hence it' ok to have a slightly modified version in use. |
One more option, but it's too complex for now, maybe it will be used later: https://github.com/minio/warp |
I tried to launch Chinglinwen's benchmark with neofs-dev-env commit 9c275da0 : [#115] Update neofs-node to v0.22.3. Current results: Looks like there is some issues with concurrency. Executed a command with a self-signed token and 4 threads:
Errors in logs of the gateway:
|
Let's try to check these errors on v0.16.0 |
Tried with dev-env: a011d670 and s3-gw: a0fb14d, received the same result:
Logs of the gw:
|
It seems that some of the errors are NeoFS related errors.
I have two concerns:
Maybe it is related to nspcc-dev/neofs-node#676 somehow. Is it hard to reproduce it in local environments? Are there any instructions for it? |
No, it's not hard, I executed like here, but appended |
We did all the tests we need for now. For automatic runs of s3 compatibility tests there will be different issue. |
Let's try to see how our gateway performs under load. I'd take Wasabi's test: https://github.com/wasabi-tech/s3-benchmark (the one used by MinIO in https://blog.min.io/s3-benchmark-using-hdd/), but we can also consider https://github.com/dvassallo/s3-benchmark. We need to:
Then our colleagues could take the document and run the same tests on more fancy hardware to get some representative results.
The text was updated successfully, but these errors were encountered: