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

About Update benchmark Setting #236

Closed
rainmaple opened this issue Jan 22, 2022 · 4 comments
Closed

About Update benchmark Setting #236

rainmaple opened this issue Jan 22, 2022 · 4 comments

Comments

@rainmaple
Copy link

if i want to use all params in validation_params.csv , which was producted by using update streams. How many operation_count i need to set when i set up benchmark.properties?

@szarnyasg
Copy link
Member

Hi @rainmaple,

  • When you run in benchmark mode with benchmark.properties, the framework does not use validation_params.csv.
  • What is the goal with your run? If you would like to conduct a benchmark that would pass an audit, you have to run it such that the warmup lasts for at least 0.5 hours and the benchmark runs for at least 2 hours. For this, getting the correct operation_count is currently done by trial and error. There's an old issue about allowing users to specify a time range (Run benchmark based on total time, rather than operation count ldbc_snb_interactive_v1_driver#38) but this has not been addressed yet.

@szarnyasg
Copy link
Member

Feel free to open an issue if you have any further questions.

@rainmaple
Copy link
Author

rainmaple commented Feb 15, 2022 via email

@szarnyasg
Copy link
Member

The script validate.sh will take a validation_params.csv file and run its workload (reads/updates) sequentially.

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

No branches or pull requests

2 participants