You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mcap merge command currently runs entirely single-threaded. For large files
or many inputs, the bottleneck is almost always chunk compression/decompression
(especially with zstd or lz4). There is no way today to tell the CLI how many
threads or workers to use.
What I'd like
A --workers N (or --num-threads N) flag on mcap merge that lets you control
the degree of parallelism, with 0 meaning "use all available CPUs".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The
mcap mergecommand currently runs entirely single-threaded. For large filesor many inputs, the bottleneck is almost always chunk compression/decompression
(especially with
zstdorlz4). There is no way today to tell the CLI how manythreads or workers to use.
What I'd like
A
--workers N(or--num-threads N) flag onmcap mergethat lets you controlthe degree of parallelism, with
0meaning "use all available CPUs".mcap merge --workers 8 -o output.mcap a.mcap b.mcap c.mcap any ideas ?All reactions