Why is tomcat slow

Hi, yes, the issue is only for start. Today it took 2 min 40 s to start. There are no apps in confluence. Normally regarding if to focus on that or not I would agree with you. Anyway, thank you for your help. Gonchik Tsymzhitov Community Leader Mar 18, Hi Andreas Bartels , Thanks for that input. As I see, you are restarting you app very often, if that correct?

Could you provide more detail info why do you restarting very often? Andreas Bartels Mar 18, Hi, correct, well noted. This instance of confluence is running on a machine that will not operate every day.

So I will see a start that is not a restart really maybe every two or three days. This is why I want it to start as a service. And quick if possible :- This is why I was enthusiastic when I did the trial. This went very well. Sadly the production solution with the external database is worse a lot. Thank you again! Hi Gonchik, as you were trying to be very helpful I just wanted you to know that I found a solution.

I think the installation will be reliable now. This is what's most important. Thank you for your input. Suggest an answer Log in or Sign up to answer. Still have a question? Get fast answers from people who know. Bjoke: A "Bully Joke".

A Statement or action made with malicious intent - unless challenged. At which point it magically transforms into "I was just funnin'" or "What's the matter, can't take a joke? Forum: Tomcat. Tomcat is Very Slow Recently. Amitha Prabath. Optional 'thank-you' note:. Hi, I have Tomcat8 as well as Tomcat7 servers which runs on Ubuntu servers.

From three days time I noticed both Tomcat versions app deployment is drastically slow. For some server when I restart the server two times the problem solves to some extent but it prevails after some period.

Asked 9 years, 2 months ago. Active 2 years, 4 months ago. Viewed 43k times. Entering midnight slowness is still maintained only 1 user online The solution I have is to restart the Tomcat service and response time is again excellent. Is there anyone who has experienced this issue? Any clue would be appreciated. Improve this question. Roman C Alejo Rlz Alejo Rlz 1 1 gold badge 1 1 silver badge 4 4 bronze badges. Session bloat. From your description, it seems your user sessions don't expire.

Look in the tomcat admin interface where you can view each deployed webapp and view the number of active sessions. You'll probably find an unreasonable number of active sessions.

Also look to make sure you're not just stuffing too much into the session — kolossus. Add a comment. Active Oldest Votes. Not enough details provided. Which application is eating the CPU? Disk Use df -h to check disk usage.

You're doing it right :D Logs Logs are awesome. Improve this answer. For performance related issue , we need to follow the given rules: You can equalize and emphasize the size of xms and xmx for effectiveness. If there any database related issue, then can follow sql query perfomance tuning rotating the Catalina. In details,There are two ways. See more at: Tomcat Catalina Out. Community Bot 1 1 1 silver badge. SkyWalker SkyWalker ShaikhAzhar : So problem is not actually size related.

So, I feel that the number 5 will be the best way. As you said, you need to restart, so we can avoid it by 5.

If your JVM supports both green and native threads, you should try both models to determine the best choice for your site.

However, green threads will decrease the load placed on your machine. If you are unsure which option to choose, native threads are usually a good choice.

Certain JVM processes, such as garbage collection and memory reallocation, can be a drain on your server. You can reduce the frequency with which these processes occur by using the -Xmx and -Xms switches to control how JVM handles its heap memory. This will free up CPU time for the processes you really care about. To maximize the effectiveness of this technique, use the -Xms switch to ensure that the JVM's initial heap memory size is equal to the maximum allocated memory.

This will keep the Tomcat JVM from having to reallocate and resize its heap memory, which will free up additional CPU cycles for Tomcat to serve requests.

If your web applications can handle the possibility of lower total garbage collection throughput, you should try enabling incremental collection with -Xincgc. If you need more information on the way your current configuration is handling your collection load, use -verbose:gc to capture performance data. Basing your maxThreads Connecter thread pool settings on an accurate estimation of your web request load is essential for getting the most out of Tomcat.

Values that are too small can leave you without enough threads to handle all your requests, and prevent Tomcat from effectively utilizing your server hardware to increase performance.

Values that are too high significantly increase Tomcat's startup time, which is a critical issue at at peak traffic intervals. Experiment with different values to determine the best middle ground, and you should see an increase in performance. By default, the compression attribute is set to off, but some applications perform better when it is switched to on.

Try changing your settings and see what works best for your site. If you find that turning compression on increases your performance, make sure you use the compressableMimeTypes setting to specify what types of data you want compressed.

However, HTTP may not be right for your site. If you require the security of HTTPS, despite its slow speed compared to HTTP, you may have to consider adding additional servers closer to your users to increase speed.