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

Should the payload always be struct? #68

Open
nsulikowski opened this issue Apr 17, 2019 · 1 comment
Open

Should the payload always be struct? #68

nsulikowski opened this issue Apr 17, 2019 · 1 comment

Comments

@nsulikowski
Copy link
Contributor

or class?

@cybertyche
Copy link
Contributor

Hello! As with all things .Net memory management, the answer tends to come down to "maybe?" The general guidance we give is to start with struct. The logic behind it is that internally to Trill we batch data into groups of up to 80 thousand. Having the data co-located like that is likely to increase throughput at least a little. However, it's not free, because the initial batching will also need to copy the structs into the payload batch.

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

2 participants