Skip to content

DRAFT: Branch for policy iteration with rocksdb. - #282

Open
tewaro wants to merge 3 commits into
mainfrom
tewaro/rocksdb
Open

DRAFT: Branch for policy iteration with rocksdb.#282
tewaro wants to merge 3 commits into
mainfrom
tewaro/rocksdb

Conversation

@tewaro

@tewaro tewaro commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Runs it with 30 random seeds first filling the database with random data
and then running the mixgraph workload. We modify the common files to
create a way to parse the output of a seeded run. At some point other
large benchmarks should be added with the same behavior and the scripts
will need to be modified. However, for the time being we just write the
script in jq. Perhaps a python parser is warranted for later. This does
generate the data in a nice comparable format.
@tewaro
tewaro requested a review from a team as a code owner August 17, 2026 06:24
@tewaro
tewaro force-pushed the tewaro/rocksdb branch 2 times, most recently from 97bddad to e78dd48 Compare August 17, 2026 07:10
@arthurp

arthurp commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

I don't think you actually wanted to request a review. There is a "draft PR" state which avoids sending automatic review requests.

I will note however, that I'm confused why this branch is needed. Iteration should be happening locally, if we don't have a good way to run the benchmark. We need to fix that. I think there should be a script already. tools/bench_....shor something.

Only choose the same two seeds so that the run takes ~10 mins.
Add t-test infra in order to check if things are different.
We will then add commit hashes to the changes to get testing to work.
@tewaro

tewaro commented Aug 17, 2026

Copy link
Copy Markdown
Contributor Author

I don't think you actually wanted to request a review. There is a "draft PR" state which avoids sending automatic review requests.

I messed up when creating the branch my bad.

I will note however, that I'm confused why this branch is needed. Iteration should be happening locally, if we don't have a good way to run the benchmark. We need to fix that. I think there should be a script already. tools/bench_....shor something.

I wanted to show the code to Gaurav to see what parts he needed to peel off for the benchmark suite. I just am pushing to this in case there is some stuff he can use. If preffered I can close this.

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

Successfully merging this pull request may close these issues.

2 participants