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

[core] Add the TimeSeriesWorkload class, a new type of workload that … #1008

Merged
merged 1 commit into from
Sep 17, 2017

Conversation

manolama
Copy link
Collaborator

…uses

the existing YCSB API to generate time series data (numeric values associated
with timestamps).
See the TimeSeriesWorkload.java class Javadocs for details on how to use it
with a client and workloads/tsworkload_template for parameters.
Also add the BasicTSDB instance for printing/debugging the workloads.

…uses

the existing YCSB API to generate time series data (numeric values associated
with timestamps).
See the TimeSeriesWorkload.java class Javadocs for details on how to use it
with a client and workloads/tsworkload_template for parameters.
Also add the BasicTSDB instance for printing/debugging the workloads.
@manolama
Copy link
Collaborator Author

Hi folks!
This is a new type of workload for testing time series databases. We've seen a ton of work around time series lately with IoT, monitoring, etc and it would be nice to get a common framework for benching.

Please take a look and let me know what you think of this framework. Particularly:

  • Help suggest standard workloads similar to the K/V A through F configs. Right now I just a tiny tsworkloada.
  • Try implementing some clients and see if parsing is acceptable.
  • Let me know if any of the TODOs or other features are really needed to adequately bench our DBs.

Thanks!

@manolama
Copy link
Collaborator Author

@jasontedor If you still have cycles, I know Elastic is working hard on time series data. Would you mind taking a look at this and give me your feedback? Thanks!

@manolama manolama mentioned this pull request Aug 11, 2017
Copy link
Collaborator

@busbey busbey left a comment

Choose a reason for hiding this comment

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

I think we're better off getting this in, calling it experimental, and iterating. We can call it non-experimental after we have a set of standard workloads.

After this goes in can we start working on docs on wiki pages (until we manage to pull all of that out of the window I guess.)

Copy link
Collaborator

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

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

I agree, I skimmed this and it looks like a good first cut.

@busbey busbey merged commit 035310c into brianfrankcooper:master Sep 17, 2017
@busbey busbey mentioned this pull request May 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants