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

Benchmarks dev guide #13

Closed
wants to merge 0 commits into from
Closed

Conversation

MiguelWeezardo
Copy link
Collaborator

Description

Is this change a fix, improvement, new feature, refactoring, or other?

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

How would you describe this change to a non-technical end user or system administrator?

Related issues, pull requests, and links

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@@ -0,0 +1 @@
1.8
Copy link
Owner

Choose a reason for hiding this comment

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

What uses this file? Shouldn't it be enough to set the required JDK in the POM?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

POM only impacts Maven, but in the README we tell developers to run java, so we can leverage jenv if they have it.

Copy link
Owner

Choose a reason for hiding this comment

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

The README should say explicitly which JDK version to use, without assuming how users manage their JDK installations.

url: http://localhost:8080
username: na
password: na
Copy link
Owner

Choose a reason for hiding this comment

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

The password should not be required by default. Maybe change the example user to benchto so it's a bit more informative than na.

--activeBenchmarks=presto/tpch --profile=presto-devenv \
--overrides overrides.yaml
# set JAVA_HOME to the JDK 8 home dir
local_repo=$(./mvnw -B help:evaluate -Dexpression=settings.localRepository -q -DforceStdout)
Copy link
Owner

Choose a reason for hiding this comment

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

Can we assume it's always $HOME/.m2/repository? That'll make the example simpler.

local_repo=$(./mvnw -B help:evaluate -Dexpression=settings.localRepository -q -DforceStdout)
java -Xmx1g \
-jar "$local_repo/io/trino/benchto/benchto-driver/0.18/benchto-driver-0.18.jar" \
--profiles.directory "." \
Copy link
Owner

Choose a reason for hiding this comment

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

This should not be necessary, the application.yaml needs to be in the current directory anyway. Maybe also remove other flags, like -Xmx1g and the time limit and paths to sql and benchmark dirs.


### Automated benchmarks

A complete script which runs a small suite of benchmarks can be found in `perftest/benchto.sh`.
Copy link
Owner

Choose a reason for hiding this comment

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

This doesn't exist (yet).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Isn't the script developed on the benchmarks branch where this PR is aimed at?

Copy link
Owner

Choose a reason for hiding this comment

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

Yes, but it should be separated from that effort so we can get this in faster.

@@ -48,8 +52,10 @@ data-sources:
environment:
name: TRINO-DEV

presto:
trino:
Copy link
Owner

Choose a reason for hiding this comment

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

You have to also either change the data source name to presto or update all benchmarks.

Copy link
Collaborator Author

@MiguelWeezardo MiguelWeezardo Sep 1, 2022

Choose a reason for hiding this comment

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

Guess I'll have to return to the old name. We can rename in a separate commit/PR

@MiguelWeezardo
Copy link
Collaborator Author

Making a separate PR not based on benchmarks branch

@MiguelWeezardo
Copy link
Collaborator Author

Continued on trinodb#13988

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.

2 participants