Default RERUN_CHUNK_MAX_BYTES to 384kiB instead of 4MiB

[teh-cmc]

• Fixes Significant performance drop after update from 0.16 to 0.18 #7222

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[nikolausWest]

Didn’t we have increase this to speed up time series?

[teh-cmc]

Didn’t we have increase this to speed up time series?

This does not affect time series since 4096 rows (RERUN_CHUNK_MAX_ROWS) of scalars still fit into 256kiB (RERUN_CHUNK_MAX_BYTES) (even when accounting for timelines, row ids, offsets, etc), with more or less margin depending on how many timelines are used.

I can probably bump it to 12 * 8 * 4096 bytes to give users even more leeway without any negative impact on the problematic workloads though. I'll try it.

[teh-cmc]

I'll try it.

Works fine.