-
Notifications
You must be signed in to change notification settings - Fork 18
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
bench: cluster patch #752
base: master
Are you sure you want to change the base?
bench: cluster patch #752
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file. | |||||
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The commit message misses a description and a link to the #645 ticket. Some things that may be useful to mention there (especially since
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Commit title is also confusing: for me There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should have tests for the feature. |
||||||
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). | ||||||
|
||||||
## [Unreleased] | ||||||
|
||||||
### Added | ||||||
|
||||||
- Tarantool benchmark tool update (cluster bench): | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To be honest, I don't get a full understanding of what "cluster" is here. It seems that one of the options for a cluster is a replicaset. No questions here. But it's more complicated with a vshard cluster. Yeah, each storage in a vshard cluster has the same schema (if we're talking about the same vshard group), so you theoretically can send the same CRUD requests to each storage in a vshard cluster. But you never work with vshard storages directly, you use a router (especially since each record from a sharded space should have a bucket id, and it's computed on a router). So it doesn't make much sense to bench storages only, especially since stored procedures on a router may be complicated and the bottleneck of the vshard clusters is often the network requests between a router and a storage. So the question is as follows. Is "cluster bench" actually a "replicaset bench"? What did you use it for? |
||||||
* option --leader has been added - sest array of url's for leaders. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
* option --replica has been added - sest array of url's for replicas. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## [2.12.4] - 2022-12-31 | ||||||
|
||||||
### Changed | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, rebase on master and resolve changelog conflict.