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

Figure out the best flush threshold for serializer based on performance and real-world use cases #32356

Closed
ahsonkhan opened this issue Feb 15, 2020 · 1 comment · Fixed by #37170
Assignees
Labels
Milestone

Comments

@ahsonkhan
Copy link
Contributor

It's currently set to flush when the buffer is 90% full.

state.FlushThreshold = (int)(bufferWriter.Capacity * .9); //todo: determine best value here

cc @steveharter

@ahsonkhan ahsonkhan added this to the Future milestone Feb 15, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Feb 15, 2020
@ahsonkhan ahsonkhan added tenet-performance Performance related issue and removed untriaged New issue has not been triaged by the area owner labels Feb 15, 2020
@layomia layomia modified the milestones: Future, 5.0 Feb 21, 2020
@layomia
Copy link
Contributor

layomia commented Feb 21, 2020

Triage: change the comment to say if we have a lot of customers with large objects and we are flushing too often, make the buffer bigger; and close the issue.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants