enhance memory usage using buffer, or avoiding alloc#153
Merged
hboutemy merged 1 commit intofusesource:masterfrom Jun 28, 2019
Merged
enhance memory usage using buffer, or avoiding alloc#153hboutemy merged 1 commit intofusesource:masterfrom
hboutemy merged 1 commit intofusesource:masterfrom
Conversation
Collaborator
|
good idea, thanks |
hboutemy
added a commit
that referenced
this pull request
Jun 29, 2019
Collaborator
|
sadly merged without testing myself and found that the patch was wrong :( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
avoid so many conversions of
char -> to String -> getChars() -> copy chars -> foreach char -> to String -> getChars ...
also use bigger buffer... as printed log line usually got more than 50 chars..
not 16 as default in StringBuilder constructor (with 16 chars, you can write "Hello World !!!!" )