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

optimize memory initialization for payload #268

Open
GitMensch opened this issue Jan 6, 2025 · 0 comments
Open

optimize memory initialization for payload #268

GitMensch opened this issue Jan 6, 2025 · 0 comments

Comments

@GitMensch
Copy link

GitMensch commented Jan 6, 2025

This applies to the "heavy" chunkdata, but also to others.

Instead of setting multiple parts of the payload to ALL x"FF" with multiple statements, do it "once" for the compete payload fields (if not dynamically), then only store the payload that is not of this value.

As the payload-size likely differs it is likely only necessary to set the whole buffer to ALL x"FF" (possibly directly with VALUE) and when the code is re-executed only set the previous payload size back to x"FF" (not the maximum buffer).

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

No branches or pull requests

1 participant