Skip to content
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

[v23.3.x] wasm/parser: bump limits #16767

Conversation

rockwotj
Copy link
Contributor

@rockwotj rockwotj commented Feb 28, 2024

Backport of PR #16722

Manual changes: fix #includes to 23.3 import paths.

@rockwotj rockwotj added this to the v23.3.x-next milestone Feb 28, 2024
@rockwotj rockwotj added the kind/backport PRs targeting a stable branch label Feb 28, 2024
@rockwotj rockwotj self-assigned this Feb 28, 2024
@rockwotj rockwotj added the area/wasm WASM Data Transforms label Feb 28, 2024
@rockwotj rockwotj linked an issue Feb 28, 2024 that may be closed by this pull request
We've seen our launch demo run into these limits, so make the containers
non-contiguous and allow up to 1MiB of memory usage during parsing. This
fits the compiled ML framework's function count (~17k), as now we allow
~21k functions.

Signed-off-by: Tyler Rockwood <rockwood@redpanda.com>
(cherry picked from commit d07f775)
@rockwotj rockwotj force-pushed the vbotbuildovich/backport-16722-v23.3.x-916 branch from f6f01b8 to 611b77a Compare February 28, 2024 10:44
@github-actions github-actions bot removed the area/wasm WASM Data Transforms label Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[v23.3.x] wasm/parser: bump limits
3 participants