19-20 MB Heap memory.Ībove, the Grizzly http server sets 16 threads listening requests and 9 NIO threads for consumers. The configured thread pool is 4 threads with queuing.Ībove, Asynchronous service. 16 MB) but I prefer to allocate some memory for concurrency. This service can start with even less memory (e.g.

That means that the service can start with only 50% of allocated memory needed for a plain Spring Boot service. It started with these settings: -Xms8M -Xmx32M -Xss4M -XX:+CMSClassUnloadingEnabled Probably its behavior is better with some load. Honestly, I expected something else from Undertow at this stage. 40-48 MB Heap memory allocated just for starting. So, the minimum required was: -Xms32M -Xm圆4M -Xss8M -XX:+CMSClassUnloadingEnabled We noticed Spring Boot is unable to start with such as memory parameters for the JVM These settings were not valid as the application had not enough memory to start. In this case we started with minimal settings: -Xms16M -Xmx32M -Xss4M -XX:+CMSClassUnloadingEnabled The machine for tests was Linux Ubuntu 16, Kernel 4.4.0-71-generic, 16GB Memory, SSD Ext4 FS. This service is actually connecting to Github REST API for demo purposes but is not relevant for the comparative. Our old Asynchronous Microservice contains the Grizzly http server, Jersey implementation of JAX-RS (implementation of the JEE specification JSR 339: JAX-RS 2.0: The Java API for RESTful Web Services) and HK2 as an implementation of the JSR-330, Dependency Injection for Java. Moreover, we have used Tomcat and Undertow in order to detect any difference. spring-boot-starter-parent 1.5.2.RELEASE spring-boot-starter-web spring-boot-starter-test test json-path test The dependencies are the Spring Boot parent on, json-path for tests and 2 starters: Spring Boot Test and Web. It is basically a REST service saying Hello to a request. It does not contain any logic and is not consuming any other service.

The microservice receives a message, processes it sends some message somewhere and returns the response to the requester.įirstly, we have used Spring Boot gs rest service for our comparative. I mean, a specific and common type that are actually intermmediators between us and an external service. Just some REST services + do something + REST client. The microservice does not contain any business logic.There are other options that will be handled in future posts. Spring Boot is right now a very extended option to compose any kind of microservices. However, this service was created bearing in mind it should be as light as possible, using JEE specifications implementations. This microservice was created as a demo to compare synchronous vs several types of asynchronous REST clients.

In this post we’ll compare only the most recent version of Spring Boot (1.5.2-RELEASE) and the custom JEE microservice based on reference implementations we built two years ago.

Gc overhead limit exceeded anylogic