-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Support for visualization of ShardingSphere performance #2908
Comments
I think the scenarios should include:
Access(3) * Mode(14) * SQL(4) = 168 secnarios For the 3.x don't support encryption, we can't show the comparison of this part. Besides, I suggest that we illustrate the performance promotion to user by using ShardingSphere.
Access(3) * Mode(1) * SQL(4) = 12 secnarios When the database is under significant stress, horizontally shard data into more databases will improve the performance. |
We can push benchmark data to https://github.com/OpenSharding/shardingsphere-benchmark |
I have created an offical Apache repo https://github.com/apache/incubator-shardingsphere-benchmark |
Jenkins only can upload a simple picture which is not enough to display performance. Frontend:
Backend:
|
@terrymanu according to your idea, we will optimize it. |
add ajax gets data,Just update the data to avoid repackaging the build。apache/shardingsphere-benchmark#4 |
1、add overview page apache/shardingsphere-benchmark#5 Finish 3 and 5 |
add new scenarios
|
Optimize details: |
Feature Request
Is your feature request related to a problem?
Describe the feature you would like.
we want to provide the perfomance data of shardingsphere with different scenarios. To implement this, different performance test scenarios which can be treated as benchmarks will be designed, and then we will submit performance data to jenkins daily, so that performance data can be achieved when shardingsphere is updated. As our design, the performance comparison of mysql, shardingsphere 4.0 and 3.0 will be provided depending on the scenarios as well.
The text was updated successfully, but these errors were encountered: