Which kind of quotation mark is more efficient?

Question

Just curious, which is more efficient?

This:

String a = someString + "." + anotherString;

Or this:

String a = someString + '.' + anotherString;

Answer 1

You really shouldn't care, unless this is all you do, thousands of times per second, for several hours.

Rumor has it that using a StringBuilder is the fastest.

Try it both of them, running in a loop, a million times, and logging the time it takes, then report back to the rest of us.

Answer 2

Looking at the code for StringBuilder.append and AbstractStringBuilder.append, I would expect the '.' form to be faster.

It has less to do, basically:

• It doesn't need to do a nullity check, as the char cannot be null
• It doesn't try to do an optimisation for an empty string being appended
• It doesn't need to fetch the length to be added - it will always be 1
• It only has to perform a single assignment into the array rather than a single-iteration loop

Like everyone else though, I wouldn't expect the difference to be significant in real application code.

I don't know whether it would be valid for the Java compiler to realise that what's being appended is a constant string of length 1, and convert that into a character literal instead - or whether it would bother doing so even if it would be valid.

Answer 3

They are pretty similar. '.' is slightly faster, but the difference is negligible ( about 20 ms in a 10 million loop ) .

Here's my test:

$cat UsingC.java  UsingS.java  
public class UsingC { 
    public static void main( String [] args ) { 
        String someString  = "";
        String anotherString = "";

        int i = 0;
        while( i++ < 10000000 ) { 
            String a = someString + '.' + anotherString;
        }
    }
}
public class UsingS{ 
    public static void main( String [] args ) { 
        String someString  = "";
        String anotherString = "";

        int i = 0;
        while( i++ < 10000000 ) { 
            String a = someString + "." + anotherString;
        }
    }
}
$for i in 1 2 3 4 5 ; do time java UsingC; done

real    0m1.643s
user    0m1.424s
sys 0m0.108s

real    0m1.670s
user    0m1.468s
sys 0m0.056s

real    0m2.023s
user    0m1.448s
sys 0m0.080s

real    0m1.669s
user    0m1.432s
sys 0m0.088s

real    0m1.674s
user    0m1.416s
sys 0m0.104s
$for i in 1 2 3 4 5 ; do time java UsingS; done

real    0m2.344s
user    0m1.584s
sys 0m0.136s

real    0m2.057s
user    0m1.640s
sys 0m0.084s

real    0m2.112s
user    0m1.732s
sys 0m0.072s

real    0m2.482s
user    0m1.704s
sys 0m0.108s

real    0m2.134s
user    0m1.788s
sys 0m0.072s

You can do an average and/or create a more complex test.

They both use StringBuilder internally anyway.

Answer 4

The Java compiler will turn any string concatenation expression into an equivalent sequence of StringBuilder operations. It is safe to assume that the sequence will be close to optimal. Indeed, in this particular example, I'd expect the same (optimal) sequence to be generated in both cases. But even if this is not the case, the difference is likely to be small.

It is only worth bothering about this sort of thing if the profiler tells you that a particular statement is a bottleneck in your code. Premature optimization is pointless (at best) and can even be harmful.

The advice of the Sun folks is that hand optimize Java code can actually be slower code because the resulting bytecode sequence becomes too complex for the JIT compiler to be able to optimize properly. The best advice is just to write the code simply and trust the Javac and JIT compilers to do a good job.