Skip to main content

String vs. StringBuffer vs. StringBuilder

We all know that using StringBuffer to perform String concatenations is far more efficient than conctenating strings using the '+' operator. Since JDK 1.5 a new class called StringBuilder has been added. StringBuilder is just like StringBuffer, except that it's methods are not synchronized. You should use StringBuilder to improve your performance if you do not need thread safety.

Shown below is an example that concatanates 10000 strings using the '+'  operator, StringBuffer, and StringBuilder, and prints the operation time in nanoseconds. The ability to get time in nanoseconds is another feature that was added in JDK 1.5.

package biz.adaptivesoftware.examples.string;

public class StringConcatanations {
  public static final int MAX_ITER = 10000;
  public static void main(String[] args) {
  public static void concatenate() {
    System.out.println("Concatanating using the + operator");
    String s1 = "";
    long s1Time = getNanoTime();
    for(int i=0;i<MAX_ITER;i++) {
      s1 = s1 + "abc";
    long e1Time = getNanoTime();
    System.out.println("Time: " (e1Time - s1Time));
  public static void concatenateWithStringBuffer() {
    System.out.println("Concatanating using StringBuffer");
    StringBuffer sb = new StringBuffer();
    long s2Time = getNanoTime();
    for(int i=0;i<MAX_ITER;i++) {
    long e2Time = getNanoTime();
    System.out.println("Time: " (e2Time - s2Time));
  public static void concatenateWithStringBuilder() {
    System.out.println("Concatanating using StringBuilder");
    StringBuilder sBuilder = new StringBuilder();
    long s3Time = getNanoTime();
    for(int i=0;i<MAX_ITER;i++) {
    long e3Time = getNanoTime();
    System.out.println("Time: " (e3Time - s3Time));
  public static long getNanoTime() {
      return System.nanoTime();



Concatanating using the + operator
Time: 744597428
Concatanating using StringBuffer
Time: 1685131
Concatanating using StringBuilder
Time: 1317206
As you can see, if you do not need thread safety, StringBuilder yeilds the best result, followed by Stringuffer, followed by the '+'  operator. However, if you do need thread safety, then StringBuffer is your natural choice.
Recommended Books:

Notes: This text was originally posted on my earlier blog at


J. Gleason said…
I am using groovy, changed it a little and now I am seeing more negligible results. I tried to make them as apples to apples as possible so I also called .toString after everything (since technically that should be done in order to create the string object).

Here are my new results (although this was done in groovy).

Time: 416136305
Time: 396484439
Time: 385318754

I think this just goes to show that there are cases (such as single appends) when using + may be just as fast and more readable. However, if you are going to be using for loops then I think you are correct here.


public class StringConcatanations {
public static final int MAX_ITER = 100000;

public static void main(String[] args) {
Long start = 0
start += concatenate();
println("Time: " + start);
start = 0

start += concatenateWithStringBuffer();
println("Time: " + start);
start = 0
start += concatenateWithStringBuilder()
println("Time: " + start);

public static Long concatenate() {
String s1 = "";
Long s1Time = getNanoTime();
s1 = s1 + "abc";
Long e1Time = getNanoTime();
return (e1Time - s1Time);

public static Long concatenateWithStringBuffer() {
StringBuffer sb = new StringBuffer();
long s2Time = getNanoTime();
String returnValue = sb.toString()
long e2Time = getNanoTime();
return e2Time - s2Time;

public static Long concatenateWithStringBuilder() {
//System.out.println("Concatanating using StringBuilder");
StringBuilder sBuilder = new StringBuilder();
Long s3Time = getNanoTime();
String returnValue = sBuilder.toString()
Long e3Time = getNanoTime();
return (e3Time - s3Time);

public static long getNanoTime() {
return System.nanoTime();

Parag said…
Hi Jackie,

That's a nice example. I wonder if Groovy uses StringBuffer internally for concatening String (even when the + operator is used).

The main benefit of String is immutability which differentiate it from Stringbuffer but in case of string manipulation this advantage becomes biggest disadvantage and creates lots of garbage also using "+" operator for String concatanation is very slow as compared to StringBuffer.append()method which cost you some performance.

source: Difference among String vs StringBuffer vs StringBuilder
Gulzar said…
Nicely explained by quoting examples to described string, stringbuffer and string builder in Java programming coding. This is excellent work done by the blogger. This is perfect blog to learn by the students of Programming.

Popular posts from this blog

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar