Java built-in data types (performance issues)
30 May 2008Java built in data types provide programmers ease of storing their required data in appropriate data type. But in come cases, it may become a bottleneck. When doing low level related work, the speed is very important. In such case don’t use the Java built-in data types.
Lets take an example. If you are using an Integer class, just think of all the overhead you are creating by using the wrapper class. One rule of thumb is to use the primitives instead of wrapper. This will guarantee better performance. In our daily life, we do not consider using unsigned int or unsigned long because Java application that we are creating are fast enough and we don’t really care about such things.
Performance is of concern when you are dealing with databases. In such cases, you should be using primitives to achieve speed and performance. They manipulate the bits directly which gives the max possible performance.
Related Posts:
- Java IO tasks
- Java performance Issues (I)
- Performance issues related to Look and Feel of GUI
- Vector Capacity
- Performance issues related to trigonometric functions , floating point arithmetic and JNI (I)
- Java performance Issues (III) - Garbage collection
- Autoboxing And Unboxing in Java 5
- Performance Issues (String Concatenation)
- Java performance Issues (IV) - Hardware interfacing
- Performance Issues (StringTokenizer)
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: Java built-in data types (performance issues)
