-
Notifications
You must be signed in to change notification settings - Fork 202
Docs: README update to help new users #370
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
base: main
Are you sure you want to change the base?
Changes from 1 commit
3c3607d
5739de6
44fac74
f6a9465
1605b46
5da6c30
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,7 @@ BenchBase (formerly [OLTPBench](https://github.com/oltpbenchmark/oltpbench/)) is | |
|
||
**Table of Contents** | ||
|
||
- [Prerequisites](#prerequisites) | ||
- [Quickstart](#quickstart) | ||
- [Description](#description) | ||
- [Usage Guide](#usage-guide) | ||
|
@@ -16,6 +17,13 @@ BenchBase (formerly [OLTPBench](https://github.com/oltpbenchmark/oltpbench/)) is | |
|
||
--- | ||
|
||
## Prerequisites | ||
|
||
Java 17 needs to be installed on the system in order to run the benchbase commands. | ||
|
||
It can be downloaded directly from the [official download page.](https://www.oracle.com/java/technologies/downloads/#java17) | ||
|
||
|
||
## Quickstart | ||
|
||
To clone and build BenchBase using the `postgres` profile, | ||
|
@@ -151,6 +159,17 @@ mvn clean compile exec:java -P postgres -Dexec.args="-b tpcc -c config/postgres/ | |
|
||
this is equivalent to the steps above but eliminates the need to first package and then extract the distribution. | ||
|
||
### How to configure Database access | ||
|
||
The configuration files located in the `/config` folder define the username and password needed to connect to the databases. They can be adapted on a global level by editing the `*_config.xml` files of the corresponding database. | ||
|
||
If there is already a built distribution, the config can also be adapted directly in the `/config` folder of the build. | ||
|
||
```xml | ||
<username>admin</username> | ||
<password>password</password> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IMO, these are the obvious ones and somewhat self explanatory. We should probably have additional docs on what the other fields in those configs do and how to adjust them. For instance, it's possible to run on a select set of queries, or multiple workload phases with a single config, but that isn't super obviously documented IMO. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can see that they look obvious to experienced users but they are needed for a quick-start of benchbase so I'd like to keep them here if possible :) Do you think it would be beneficial to add a new .README file to the config folder and explain the advanced things there? - Or move everything related to config there and add a quick navigation link to the new .README file in the github README? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My point about those two parameters being obvious is that they're self explanatory once you know where to look, but the part about where the configs are may not be. I would suggest that the Getting Started text get rewritten as something slightly more high-level like "adjusting the connection details in the config file" which includes basic commentary about both the JDBC URL and the credentials. A separate I don't think the entire Make sense? |
||
``` | ||
|
||
### How to Enable Logging | ||
|
||
To enable logging, e.g., for the PostgreSQL JDBC driver, add the following JVM property when starting... | ||
|
Uh oh!
There was an error while loading. Please reload this page.