Skip to content
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

Range scans/v1 #1

Merged
merged 3 commits into from
Apr 25, 2018
Merged

Range scans/v1 #1

merged 3 commits into from
Apr 25, 2018

Conversation

denesb
Copy link
Contributor

@denesb denesb commented Apr 25, 2018

Add basic support for range scans.

denesb added 3 commits April 25, 2018 06:48
Printing the results table with tabs proved very unreliable. The columns
in some rows would often wider then expected and would push all other
columns to the right making the table almost impossible to read.
Instead use fmt.Printf() to print the table header and each line and
define a reasonable width for each column.
Add a new mode "scan" which executes a full table scan. Later we might
add options to do partial scans.
The "scan" mode doesn't use a worload unlike all the other modes.
@@ -91,6 +91,16 @@ SELECT * from %s.%s WHERE pk = ? AND ck IN (?, ...)

Counter read mode works in exactly the same as regular read mode (with the same configuration flags available) except that it reads data from the counter table `scylla_bench.test_counters`.

#### Scan mode (`-mode scan`)

Scan the entire table. This mode does not allow the `workload` to be configured. It is important to note that range-scans put a significant load on the cluster and also take a long time to complete.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At some point we may want to make this more configurable and not just limited to full table scans, but so far scylla-bench has been developed lazily by implementing only what was actually needed and there is no need to change that approach, especially since those changes could be done incrementally without any major rewrites.

@pdziepak pdziepak merged commit 1b9bba8 into scylladb:master Apr 25, 2018
@denesb denesb deleted the range-scans/v1 branch October 4, 2018 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants