Several of us might be familiar with the clear () API in Java collections framework. In this post, let’s discuss what is the purpose of this clear() API? What is the performance impact of using this API? What happens under the JVM when this API is invoked?
Continue reading “Clear details on Java collection ‘Clear()’ API”
JVM memory has following regions:
Fig: JVM memory regions
a. Young Generation
b. Old Generation
c. Metaspace
d. Others region
Continue reading “Chaos Engineering – Metaspace OutOfMemoryError”
JVM Memory has following regions:
a. Young Generation
b. Old Generation
c. Metaspace
d. Others region
Continue reading “Inspect the contents of the Java Metaspace region”
java.lang.String#intern() is an interesting function in Java. When used at the right place, it has potential to reduce overall memory consumption of your application by eliminating duplicate strings in your application. To learn how intern() function works, you may refer to this blog. In this post let’s discuss the performance impact of using java.lang.String#intern() function in your application.
Continue reading “Java String intern: Performance impact”
intern() is an interesting function in java.lang.String object. intern() function eliminates duplicate string objects from the application and has potential to reduce overall memory consumption of your application. In this post, let’s learn more about this intern() function.
Continue reading “Java String intern(): Interesting Q & A”
intern() is an interesting function in java.lang.String object. intern() function eliminates duplicate string objects from the application and has potential to reduce overall memory consumption of your application. To understand how string intern() function works you may refer to this interesting blog. Intern strings are stored in a string pool in the JVM memory. JVM Memory has following regions:
Continue reading “In which region intern strings are stored?”
There are a good number of articles that articulate functional differences between HashMap, HashTable and ConcurrentHashMap. This post compares the performance behavior of these data structures through practical examples. If you don’t have patience to read the entire post, here is bottom line: When you confront with the decision of whether to use HashMap or HashTable or ConcurrentHashMap, you can consider using ConcurrentHashMap since it’s thread-safe implementation, without compromise in performance.
Continue reading “Java Hashtable, HashMap, ConcurrentHashMap – Performance impact”
When we launch applications, we specify the initial memory size and maximum memory size. For the applications that run on JVM (Java Virtual Machine), initial and maximum memory size is specified through ‘-Xms’ and ‘-Xmx’ arguments. If Java applications are running on containers, it’s specified through ‘-XX: InitialRAMPercentage’ and ‘-XX: MaxRAMPercentage’ arguments. Most enterprises set the initial memory size to a lower value than the maximum memory size. As opposed to this commonly accepted practice, setting the initial memory size the same as the maximum memory size has certain ‘cool’ advantages. Let’s discuss them in this post.
Continue reading “Benefits of setting initial and maximum memory size to the same value”
I am slightly hesitant to write this post, as it might attract some criticism. Nevertheless, I told myself there is nothing wrong with sharing my point of view (even though it might not be well accepted). I would like to share my personal experience regarding yesterday’s Monolithic and today’s Microservice architecture in this post.
Continue reading “Is today’s microservice more bloated than yesterday’s monolith?”
Naveen Kumar Namachivayam from QAInsights Invited Ram Lakshmanan – The architect of yCrash to talk in the Performance Engineers Clubhouse. In this video, the basics of Garbage collection, Importance of Memory, GC Throughput Introduction and many other topics have been discussed!
