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

workload: use workload split functionality with tpcc #35511

Merged
merged 1 commit into from
Mar 7, 2019

Conversation

ajwerner
Copy link
Contributor

@ajwerner ajwerner commented Mar 7, 2019

Before this PR the tpcc workloads dealt with splitting ranges on their own.
This splitting logic lacked the sophistication built in to the workload package
split implementation which works to mitigate imbalance.

Fixes #25872.

Release note: None

@ajwerner ajwerner requested a review from danhhz March 7, 2019 18:48
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@danhhz danhhz left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @ajwerner and @danhhz)


pkg/workload/tpcc/tpcc.go, line 333 at r1 (raw file):

	}

	const warehousesPerRange = 10

I have a weak preference for sticking all these constants next to the numXPerY in generate.go

@ajwerner ajwerner force-pushed the ajwerner/splits-with-tpcc branch from 2ca56cb to b52153d Compare March 7, 2019 19:03
Copy link
Contributor Author

@ajwerner ajwerner left a comment

Choose a reason for hiding this comment

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

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale)


pkg/workload/tpcc/tpcc.go, line 333 at r1 (raw file):

Previously, danhhz (Daniel Harrison) wrote…

I have a weak preference for sticking all these constants next to the numXPerY in generate.go

Done.

Before this PR the tpcc workloads dealt with splitting ranges on their own.
This splitting logic lacked the sophistication built in to the workload package
split implementation which works to mitigate imbalance.

Fixes cockroachdb#25872.

Release note: None
@ajwerner ajwerner force-pushed the ajwerner/splits-with-tpcc branch from b52153d to 334a88f Compare March 7, 2019 19:34
@ajwerner
Copy link
Contributor Author

ajwerner commented Mar 7, 2019

bors r+

@craig
Copy link
Contributor

craig bot commented Mar 7, 2019

Merge conflict (retrying...)

craig bot pushed a commit that referenced this pull request Mar 7, 2019
35511: workload: use workload split functionality with tpcc r=ajwerner a=ajwerner

Before this PR the tpcc workloads dealt with splitting ranges on their own.
This splitting logic lacked the sophistication built in to the workload package
split implementation which works to mitigate imbalance.

Fixes #25872.

Release note: None

35512: c-deps: bump rocksdb for bottommost files bug fix r=ajkr a=ajkr

Pick up cockroachdb/rocksdb#26

Release note: None

35519: sql: fix a non-deterministic test r=knz a=knz

Release note: None

35520: build: Fix docker link for alpha/beta builds r=knz a=bdarnell

Release note: None

Co-authored-by: Andrew Werner <[email protected]>
Co-authored-by: Andrew Kryczka <[email protected]>
Co-authored-by: Raphael 'kena' Poss <[email protected]>
Co-authored-by: Ben Darnell <[email protected]>
@craig
Copy link
Contributor

craig bot commented Mar 7, 2019

Build succeeded

@craig craig bot merged commit 334a88f into cockroachdb:master Mar 7, 2019
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.

3 participants