-
Notifications
You must be signed in to change notification settings - Fork 3
feat: Gc benchmarking #421
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
Draft
stanbrub
wants to merge
61
commits into
deephaven:main
Choose a base branch
from
stanbrub:gc-benchmarking
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
61 commits
Select commit
Hold shift + click to select a range
9d490f5
Disabled some benchmarks and scaled
stanbrub 47f066f
Scaled up basic math combo
stanbrub dea74d7
Merge branch 'deephaven:main' into gc-benchmarking
stanbrub 15cf1f4
Added a Local Parquet Generator as opposed to going through Kafka
stanbrub 8604111
Added local parquet generator and 1st training test
stanbrub 83b1c11
Added more train benchmarks. Improved Local Parquet Generator
stanbrub c552c01
Revert BasicMathCombo
stanbrub 62aa96a
Revert BasicMathCombo
stanbrub f78ca22
Reverted scale and disabled for pre-train standard tests used for pre…
stanbrub e5412e7
Parallelized local parquet. worked around directory link failures
stanbrub ff4d891
Added 1st pass at benchmark even retrieval with JFR
stanbrub f35ab4f
Merge branch 'deephaven:main' into gc-benchmarking
stanbrub 25629cc
Added jfr events
stanbrub 254cca0
Merge branch 'deephaven:main' into gc-benchmarking
stanbrub 528c365
Added UGP events
stanbrub bd5ff02
Rescaled only static trained for 120 secs
stanbrub 75449bb
Updated adhoc for local parquet env variables
stanbrub ec2d95e
Open up dh data dir so local parquet can work
stanbrub a402a54
More logging for benchmark runs
stanbrub 4cf8357
Scaling back AggBy because of system lockup
stanbrub 8507794
Restrict the number of parquet threads and memory for the runner
stanbrub c0b5e7a
Fixed NaturalJoin OOM
stanbrub 8f1a77f
Added separate scalling for static vs inc
stanbrub 2938992
Better separation for running static and inc. Added ugp deltas
stanbrub 9b326e0
turn on JFR metrics
stanbrub 7fe14cc
Turn off Inc runs
stanbrub 5e1d59c
Added ss_log budget metric
stanbrub a1316d4
Added runner setting for auto tune cycle factor
stanbrub af3d82b
G1 inc release max
stanbrub 28745a8
ParallelGC inc release max
stanbrub ac0c87f
Shenandoah GC inc release max
stanbrub 9d630d9
ZGC inc release max
stanbrub dfa44df
Inc release filter min
stanbrub 3ab1845
Updated for 100ms cycle at 90% min
stanbrub e0e763f
Added state log ugp times
stanbrub 4fd604a
Pared down to two Filter/Nat tests
stanbrub 07eacdf
Scaled for 1 sec cycles
stanbrub 90e7153
Set autotune to 90% target release
stanbrub f18c994
User JVM 25 for adhoc
stanbrub 8240602
Added update listener cycle times instead of server state log ones
stanbrub 9951735
Set 20% inc release
stanbrub 7c18a2c
Change inc release to 40%
stanbrub ce992b3
Change inc release to 60%
stanbrub fcde3fa
Change inc release to 80%
stanbrub ff2795a
Change inc release to 100%
stanbrub 60839de
Run 50ms against zfc
stanbrub d18049c
Make release filter table smaller based on inc release factor
stanbrub c43719a
Change inc release to 40%
stanbrub 45d5314
Change inc release to 20%
stanbrub 36b1e83
Change inc release to 40%
stanbrub d4e0255
Change inc release to 60%
stanbrub 1b351a5
Change inc release to 80%
stanbrub 4f4124a
Change inc release to 100%
stanbrub 11dbba7
Scale for Java 25
stanbrub c048170
Roll back changes some unwanted changes
stanbrub c9af58a
Switch to java 17
stanbrub 5364601
Change to JVM 25
stanbrub 4af7393
Rescaled for 100ms benchmarks
stanbrub 920c89c
Changed autotune to 90% for testing
stanbrub 37dc336
Add 1.10% inc target
stanbrub c6f4a00
Turn off static for now. Do inc 100p
stanbrub File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we can't use the timestamp from the file? I have a few worries about doing rowset calculation as part of the benchmark (to come up with ii).
For the actual test benchmarks, without a select we would also just prefer more/bigger parquet files to avoid the overhead of going through the merge data structures. We might even be able to get away with symlinks to have the data just repeate itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the "train" benchmarks, since we don't use Scale Factors, that section of code will not be hit. This is only used when we are doing merges to simulate larger data sets. So for the nightly runs, this will happen BEFORE the "select" into memory, which is not included in the measurement. But for the "train" benchmarks, we only read timestamps directly from the parquet file(s), and that only if they are used in the benchmark (like for rollingtime).