Skip to main content

A Quick Java Decompilers Comparison in the Case of String Concatenation

Introduction


Java decompilers are great tools to give insight about efficiency of compiled code. Currently there are two popular java decompilers: cavaj and jd-gui.

Comparison Case


It is a well-known fact that concatenation of strings is not an efficient way of building strings using some number of other string obects. Since string objects are immutable, each concatenation creates a new string, this will continue until final string object is created. All created string objects other than the final one, are intermediate objects and nothing but garbage.
For this reaseon java compiler converts string concatenations into StringBuilder statements. Using decompilers lets see if this is really true.
Below are the original source code and decompiled versions of original code using two decompilers.

// original source code
logger.debug("bulkId:" + bulkId + " is TIME_RULES_VIOLATED...");
logger.debug(new StringBuilder("bulkId:").append(bulkId).append(" is TIME_RULES_VIOLATED...").toString());

// decompiled using jd-gui
logger.debug("bulkId:" + bulkId + " is TIME_RULES_VIOLATED...");
logger.debug("bulkId:" + bulkId + " is TIME_RULES_VIOLATED...");

// decompiled using cavaj
logger.debug((new StringBuilder()).append("bulkId:").append(bulkId).append(
       " is TIME_RULES_VIOLATED...").toString());
logger.debug((new StringBuilder("bulkId:")).append(bulkId).append(" is TIME_RULES_VIOLATED...").toString());

Original source code consists of two log lines which prints the same thing but using different ways to see differences in decompiler behaviours.

Consider the first line: jd-gui shows it as if compiler never touches the string concatenations. On the other hand cavaj displays a StringBuilder usage. Which one is the actual one. Does jd-gui assume that all StringBuilder expressions in byte code are actually string concatenations?

Consider the second line: jd-gui displays the same string concatenation statement, while cavaj decompiles without changing the way it is formed. As a result, jd-gui’s assumption stated above holds true.

Conclusion


Java compiler really converts String concatenations into StringBuilder expressions. Since string concatenations are compiled as StringBuilder expressions, in source code using string concatenations instead of StringBuilders is preferable. Because string concatenations are more readable.  
Finally in terms of reflecting actual compiled code cavaj works better.
Labels:

Comments

Post a Comment

Popular posts from this blog

Obfuscating Spring Boot Projects Using Maven Proguard Plugin

Introduction Obfuscation is the act of reorganizing bytecode such that it becomes hard to decompile. Many developers rely on obfuscation to save their sensitive code from undesired eyes. Publishing jars without obfuscation may hinder competitiveness because rivals may take advantage of easily decompilable nature of java binaries. Objective Spring Boot applications make use of public interfaces, annotations which makes applications harder to obfuscate. Additionally, maven Spring Boot plugin creates a fat jar which contains all dependent jars. It is not viable to obfuscate the whole fat jar. Thus obfuscating Spring Boot applications is different than obfuscating regular java applications and requires a suitable strategy. Audience Those who use Spring Boot and Maven and wish to obfuscate their application using Proguard are the target audience for this article. Sample Application As the sample application, I will use elastic search synch application from my GitHub repository.
4 comments
Read more

Hadoop Installation Document - Standalone Mode

This document shows my experience on following apache document titled “Hadoop:Setting up a Single Node Cluster”[1] which is for Hadoop version 3.0.0-Alpha2 [2]. A. Prepare the guest environment Install VirtualBox. Create a virtual 64 bit Linux machine. Name it “ubuntul_hadoop_master”. Give it 500MB memory. Create a VMDK disc which is dynamically allocated up to 30GB. In network settings in first tab you should see Adapter 1 enabled and attached to “NAT”. In second table enable adapter 2 and attach to “Host Only Adaptor”. First adapter is required for internet connection. Second one is required for letting outside connect to a guest service. In storage settings, attach a Linux iso file to IDE channel. Use any distribution you like. Because of small installation size, I choose minimal Ubuntu iso [1]. In package selection menu, I only left standard packages selected.  Login to system.  Setup JDK. $ sudo apt-get install openjdk-8-jdk Install ssh and pdsh, if not already i
3 comments
Read more

Java: Cost of Volatile Variables

Introduction Use of volatile variables is common among Java developers as a way of implicit synchronization. JIT compilers may reorder program execution to increase performance. Java memory model[1] constraints reordering of volatile variables. Thus volatile variable access should has a cost which is different than a non-volatile variable access. This article will not discuss technical details on use of volatile variables. Performance impact of volatile variables is explored by using a test application. Objective Exploring volatile variable costs and comparing with alternative approaches. Audience This article is written for developers who seek to have a view about cost of volatile variables. Test Configuration Test application runs read and write actions on java variables. A non volatile primitive integer, a volatile primitive integer and an AtomicInteger is tested. Non-volatile primitive integer access is controlled with ReentrantLock and ReentrantReadWriteLock  to compa
Post a Comment
Read more