what to use String OR StringBuilder to keep large texts?

Question

I have mulitthreaded programs that read large xmls and currently convert them to String e.g:

String temp = MyObject.convertToString(xmls);

i have to pass on this String to various methods to process it. The Question is not related to appending BUT holding/Storing this large text in an Object i.e String OR StringBuilder.

How String and StringBuilder will affect performance/memory, my thinking is that if i keep using String it will pool the string in JVM with multiple XMLS. In other case it will be an Object and will be GC'd once not required or set to null. More over what will be the behavior of Stringbuilder.toString() on memory then.

StringBuilder's purpose to build or manipulate string. If you do not manipulate your string then use string. If you worried about performence/memory of keeping and reading string - definitely use a string — Fabio
– Fabio, Commented Feb 23, 2017 at 6:28

user207421 · Accepted Answer · 2017-02-23 06:22:57Z

1

it will pool the string in JVM with multiple XMLS

Only if it's a string literal or you intern() it. No reason not to use a String here.

answered Feb 23, 2017 at 6:22

user207421

312k45 gold badges324 silver badges493 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

usman Over a year ago

that makes sense, now what will be the affect of StringBuilder.toString(), how will it look in back ground, if i used builder and then did toString() on it every time.

user207421 Over a year ago

I don't know what you mean by 'in background', but the result of toString() is a String, to which the remarks in this answer apply. As you're not appending, I don't even know why you're asking the question.

Collectives™ on Stack Overflow

what to use String OR StringBuilder to keep large texts?

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related