Updated zs3server.json to work with 72 core zs3server #192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updating default s3server.json file to work with a 72core zs3server
Motivation and Context
Set this as the default parameters so it is easier for the one-click solution setup. This works for a zs3server that has 72 cores. Also optimized batch size and wait time to ensure every batch is filled before getting flushed (reduce latency).
How to test this PR?
Run this with the Zs3 warp test : https://docs.zus.network/zus-devops/zus-network-testing/performance-test/zs3server-warp-benchmark-testing
Types of changes
Checklist: