-
-
Notifications
You must be signed in to change notification settings - Fork 955
perf(runs-replication): Improve the CPU efficiency and throughput of the runs replication to clickhouse #2866
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
Open
ericallam
wants to merge
18
commits into
main
Choose a base branch
from
perf/runs-replication
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.
Open
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
d05720c
Create performance test harness for runs replication service
ericallam 57861d3
improve test harness producer throughput and better organize run outputs
ericallam 0bf8cfa
use a less CPU-intensive way of inserting task runs
ericallam be64766
use compact insert strategy for runs
ericallam 32f758a
added back in max duration in seconds
ericallam 4f946a4
cleanup the types
ericallam df12287
simplify
ericallam 55ed118
much better type safety
ericallam 44c5267
fixed types
ericallam 284c196
fix clickhouse tests
ericallam a2fa855
really fix clickhouse tests
ericallam f8640f6
Add object-based insert functions and fix index generation
ericallam 5f40360
Fix TypeScript errors in sort functions
ericallam ca37d7e
Fix sort comparators to return 0 for equal values
ericallam d1129d7
Remove performance test harness
ericallam df3ea39
Remove remaining performance harness artifacts
ericallam b9db398
Update pnpm-lock.yaml
ericallam 4de8899
Stop dynamically loading superjson
ericallam 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
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.
🧩 Analysis chain
🌐 Web query:
ClickHouse async_insert_max_data_size setting type format string or number💡 Result:
async_insert_max_data_size is a numeric setting (bytes). Set it as an integer (e.g. 10485760). It’s the max number of bytes of buffered data before flush and is passed like async_insert_max_data_size=10485760. [1][2]
Sources
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 96
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 51
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 1387
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 93
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 755
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 119
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 4152
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 51
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 51
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 5686
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 33912
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 19004
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 851
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 51
🏁 Script executed:
Repository: triggerdotdev/trigger.dev
Length of output: 3880
🌐 Web query:
@clickhouse/client npm package async_insert_max_data_size parameter type string or number💡 Result:
The setting async_insert_max_data_size is a ClickHouse server UInt64 setting; in the @clickhouse/client TypeScript typings it appears in ClickHouseSettings (as async_insert_max_data_size?: UInt64) — effectively a number in the client. [1][2]
Sources:
Change
async_insert_max_data_sizefrom string to number.The ClickHouse setting
async_insert_max_data_sizemust be a numeric value (UInt64 bytes), not a string. TypeScript types from@clickhouse/clientexpect a number, and ClickHouse documentation specifies a numeric format. Update to:async_insert_max_data_size: 1000000(remove quotes).🤖 Prompt for AI Agents