System requirements

These are the minimal system and hardware requirements to run JLupin Platform properly with initial configuration provided by the Vendor. Note that amount of resources provided to the production environment depends on the number of applications, their individual requirements and the load of the related service. The capacity planning process could be provided as a additional service by the Vendor or its Partners.

Parameter Value
Chipset Architecture x86_64
Processor (CPU) one 2 GHz CPU minimum
Physical Memory (RAM) 2 GB - depends on server JVM memory settings
Disk Space (HDD) 500 MB (only binaries and server logs)
Operating System* Linux, Windows
Java (Main Server) Oracle JDK 8 (recommended)
Oracle JDK 9
OpenJDK 8
OpenJDK 9
Java (Microservice) Oracle JDK 7
Oracle JDK 8 (recommended)
Oracle JDK 9
OpenJDK 7
OpenJDK 8
OpenJDK 9

* Tested on:

  • Ubuntu Server 16 64-bit
  • Ubuntu Server 17 64-bit
  • Debian 8 64-bit
  • Debian 9 64-bit
  • CentOS 6.x 64-bit
  • CentOS 7.x 64-bit
  • RHEL EL 6.x 64-bit
  • RHEL EL 7.x 64-bit
  • Windows 7 64-bit
  • Windows 8 64-bit
  • Windows 10 64-bit
  • Windows Server 2012R2 64-bit
  • Windows Server 2016 64-bit

System tuning

There are some system parameter that should be taken into consideration during JLupin's environment installation and testing. These parameters are strictly depends on how much traffic the system is handling, but usually the default limits are reached very quickly and to avoid performance problem we recommend to proactively increase this parameters to levels appropriate for the amount of memory available for the system. These parameters are:

  • the maximum number of open files by a process
  • the maximum number of processes initialized by a user
  • the maximum number of connections in OS.
  • the maximum number of available TCP sockets

Linux tuning

If the node is dedicated to JLupin (on production - it should be) we recommend to tune OS by changing the following parameters (where <user> is the name of the user which starts JLupin Platform):

  • Number of open files and process for the user in limits.conf:
<user>            soft    nofile          64500
<user>            hard    nofile          64500
<user>            soft    nproc           32768
<user>            hard    nproc           32768
  • Number of sockets that are used for outbound connections through sysctl tool:
net.ipv4.ip_local_port_range = 1024 65535
  • Port reuse option for tcp through sysctl tool:
net.ipv4.tcp_tw_reuse = 1
  • Timeout for connection in TIME_WAIT state through sysctl tool:
net.ipv4.tcp_fin_timeout = 30