Server is slow after (re)deployment of a servlet

Troubleshooting

Summary

This article explains why the first call to a server after (re)deployment of a servlet is noticeably slower than subsequent calls.

Description

After deployment or redeployment of a servlet, the response time is noticeably longer on the first run than on subsequent runs.

The long delay after redeployment of a servlet (or after (re)starting the server) is due to just in time compilation and caching: If you redeploy your application the code is just plain byte code which is not loaded until it is first needed. So for the very first usage of the classes it will take longer. Also the just in time compiler and HotSpot will gradually improve the performance of the code as it detects performance bottlenecks and optimizes code. So subsequent runs will be noticably faster (possibly even the 3rd or 4th run). yFiles itself does no caching so the performance improvements are only due to the interpreter/JIT/Hotspot/class cache.

So your application is only performing less optimal for the very first usage after deployment but should then provide constantly better performance.

Categories this article belongs to:
yFiles FLEX > Using yFiles FLEX with a yFiles Server > Communicating with yFiles.NET on the Server
yFiles FLEX > Communicating with the Server > Remote Communication in yFiles FLEX
yFiles FLEX > Using yFiles FLEX with a yFiles Server > Communicating with yFiles Java on the Server
Applies to:
yFiles FLEX: 1.4, 1.5, 1.6, 1.7, 1.8
Keywords:
server - delay - response - slow