How to easier define memory wasted stuff and detect your bad scripts/apps

-

 Hi awesome community,

In this article, I would like to share with you a small tips and tricks related to analyzing heap dump using Yourkit.

First of all, disclaimer: all things should be tested on test environment. 

 

Let's do investigation. 

1. You need to take a heap dump. Let's follow https://dzone.com/articles/how-to-capture-java-heap-dumps-7-options 

Actually, I use jcmd for take heap_dump. Because jmap is mostly affected my prod instance. ;)  Time to time JVisualVM helps to me as well.

2. Then upload to your PC. (scp, rsync, nc)

2. Let's Open snapshot 

image.png

 

3. Let's click to Class and package in Right Sidebar and check your apps just for double check. 

image.png And easier you can investigate your classes and packages. Also, you can see Check which objects mostly used and wasted. 

image.png

That article helps to me https://dzone.com/articles/preventing-your-java-collections-from-wasting-memo

4. Well, let's investigate a biggest objects

image.png

 

5. Let's investigate what is this? Just click calculate GC root paths. image.png

6. Finally, it was no needed caching which was in app from marketplace.

7. Let's review "Inspections" tab. To me it is very interesting area. image.png Because after waiting all calculation you can find wasted data structures in your platform, app from vendor and your apps. 

8. Interesting to review your groovy scripts, maybe time to optimize. ;) 

image.png

9. Also, I found interesting app which used so much Regex. 

image.png

 

A small conlusion: 

0. Changed GC strategy

1. Rewrote own app 

Using that artile as start https://dzone.com/articles/preventing-your-java-collections-from-wasting-memo , I have changed the initialize the data structure values and change somewhere the data structure. e.g. Somewhere replace Hashmap into ArrayList, or with predictable init size. 

2. Noticed a few app vendors about problems. 

3. Updates to latest one or reconfigured

4. Completely removed/disabled a few apps

5. Optimized groovy scripts ( a few things was removed)

And last good thing is opening issues with integration starting so faster from 32s to ~ 6s as average. that info based on HAR files from end of users. About searching I can't provide because I don't have metrics.  VM resources I can provide also as well.

 

 

Thanks

I hope this one will be helpful for you. Next time I will share another story with other tool :)

 

Cheers,

Gonchik Tsymzhitov

Comments

Post a Comment

Popular posts from this blog

Overview and practical use cases with open source tracing tool for Java Apps. Glowroot. Installation

-
Image
In that small article, you can find how to install the agent of Glowroot. Installation of the application is quite simple on agents, and this article shows a scheme for working with a built-in collector, but for industrial installations we use it with a bundle with elasticsearch. The installation can be both for individual nodes and so for the central collector. In this case, consider for a separate node. Prerequisites: {jira_home} - is location of Jira home directory. {jira_installation_directory} is the location of Jira installation directory.   Steps: Downloading the installer wget -c https://github.com/glowroot/glowroot/releases/download/v0.13.6/glowroot-0.13.6-dist.zip To check, create a directory via command   mkdir -p /{jira_home}/glowroot/tmp Let the Jira process write and set ownership for simplicity, but it is recommended that you just give the write ability to the owner of the Jira process. chown -R jira: /{jira_home}/glowroot We additionally set the argument to setenv.sh in
Read more

Atlassian Community, let's collaborate and provide stats to vendors about our SQL index usage

-
  Hi!  Gonchik is in touch. Today I would like to get a little bit of help from you related SQL indexes on your Jira installation (Data Center, Server edition does not matter).    I would like to share a story about  PostgreSQL  and  Jira 8.13.3  ( JSD 4.13.3 )  release.  In that post I will be happy if you answer and comment about your instance indexes, as those info can help to improve the existing situation of heavy indexes.  Typically, it starts from improvement of configuration (e.g. using  https://postgresqltuner.pl/ ),  then query analyzing, adding indexes, after removing as heavy one (shortly  https://wiki.postgresql.org/wiki/Index_Maintenance ) :)    I use like this query in PostgreSQL: SELECT s.schemaname,        s.relname AS tablename,        s.indexrelname AS indexname,        pg_size_pretty(pg_relation_size(s.indexrelid::regclass)) AS index_size,        idx_tup_read,         idx_tup_fetch,         idx_scan FROM pg_catalog.pg_stat_user_indexes s JOIN pg_catalog.pg_index i O
Read more

How only 2 parameters of PostgreSQL reduced anomaly of Jira Data Center nodes

-
Image
  Hello community, Gonchik Tsymzhitov is in touch. Today, I would like to share with you a short story about postgresqltuner.pl in usage.  So from previous articles I hope you configured the PostgreSQL server and postgresqltuner.pl.  After executing command, ./postgresqltuner.pl --ssd for ssd disks server. You can see like this output: postgresqltuner.pl version 1.0.1 [OK]      I can invoke executables Connecting to /var/run/postgresql:5432 database template1 as user 'postgres'... [OK]      The user account used by me for reporting has superuser rights on this PostgreSQL instance =====  OS information  ===== [INFO]    OS: linux Version: 5.4.17-2036.102.0.2.el8uek.x86_64 Arch: x86_64-linux-thread-multi [INFO]    OS total memory: 41.03 GB [OK]      vm.overcommit_memory is adequate: no memory overcommitment [INFO]    Running under a vmware hypervisor [INFO]    Currently used I/O scheduler(s): mq-deadline =====  General instance informations  ===== -----  PostgreSQL version  -----
Read more