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

MultiPutRequest.toString is too expensive #3

Closed
tsuna opened this issue Apr 27, 2011 · 0 comments
Closed

MultiPutRequest.toString is too expensive #3

tsuna opened this issue Apr 27, 2011 · 0 comments
Labels

Comments

@tsuna
Copy link
Member

tsuna commented Apr 27, 2011

MultiPutRequest.toString is too expensive because it serializes every single edit in the MultiPutRequest. This method is called by the constructor of NotServingRegionException. In a high-throughput environment, this can waste a very significant amount of CPU cycles and cause a lot of unnecessary stress on the GC. We need to find a way to make MultiPutRequest.toString cheaper but still informative. I'm thinking of something based on the number and size of edits in the MultiPutRequest. Maybe just the size would be sufficient. If the MultiPutRequest contains less than 1k of data, render it as today, otherwise only show the first few items and then print how many items haven't been rendered in the string representation.

@tsuna tsuna closed this as completed in a5ab041 Jul 26, 2011
HeartSaVioR pushed a commit to HeartSaVioR/asynchbase that referenced this issue Oct 21, 2015
csoulios pushed a commit to pythian/asynchbase that referenced this issue Oct 23, 2015
Restore Jackson. Running integration tests requires we not exclude it.
@bigpws bigpws mentioned this issue May 16, 2018
mapr-devops pushed a commit to mapr/asynchbase that referenced this issue Feb 5, 2019
DEVOPS-740: Sync up apache:spark to mapr:private-spark
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant