GR:Gravity/Installation/Server/Requirements

From Remain Software
Jump to navigation Jump to search

Server Hardware Requirements Guide

Server administrators can use this guide in combination with the free Gravity trial period to evaluate their server hardware requirements. Because server load is difficult to predict, live testing is the best way to determine what hardware a Gravity instance will require in production.

Peak visitors are the maximum number of browsers simultaneously making requests to access or update pages in Gravity. Visitors are counted from their first page request until the connection is closed and if public access is enabled, this includes internet visitors as well as logged in users. Storage requirements will vary depending on how many items and attachments you wish to store inside Gravity.

Minimum hardware requirements

The values below refer to the minimum available hardware required to run Gravity only; for example, the minimum heap size to allocate to Gravity is 1GB. You'll need additional physical hardware, of at least the minimum amount required by your Operating System and any other applications that run on the server.

On small instances, server load is primarily driven by peak visitors, so minimum system requirements are difficult to judge. We provide these figures as a guide to the absolute minimum required to run Gravity, and your configuration will likely require better hardware.

The installed Java runtime, required to run the Gravity server or client, should be at least Java JRE/JDK version 11.

5 Concurrent Users
  • CPU: Intel Dual Core i5 (2.3 Ghz+ CPU)
  • RAM: 4GB
  • Minimum database space: 2+ GB
25 Concurrent Users
  • CPU: Intel Quad Core (2.5 GHz+ CPU)
  • RAM: 8GB
  • Minimum database space: 5+ GB


Note: Please be aware that while some of our customers run Gravity on SPARC-based hardware, we only officially support Gravity running on x86 hardware and 64-bit derivatives of x86 hardware and POWER7 and higher processors. Gravity typically will not perform well in a tightly constrained, shared environment. Please be careful to ensure that your choice of hosting platform is capable of supplying sustained processing and memory capacity for the server.

Server load and scalability

When planning server hardware requirements for your Gravity deployment, you will need to estimate the server scalability based on peak visitors.


Hard disk requirements

All page content is stored in the database, while attachments use both the database and the file system. The more attachments you have, the more disk space you will require.


Private and public comparison

Private instances manage their users either internally or through a user repository such as LDAP, while online instances have public signup enabled and must handle the additional load of guest internet visitors.

Examples

Remain Software Helpdesk (as of 21/5/2018)
  • Operational 4 years
  • 151 users in 7 roles and 13 groups
  • 1651 Items
  • 1 Application, 3 Workflows and 41 stages
  • 10000 total comments with 3337 system comments and 6663 user comments
  • 13 public filters and 18 private filters
  • 1395 Attachments
  • Server Linux
  • Database MySQL
  • Database Size 1069 MB
  • Gravity Directory Size 1GB
Remain Software Internal Project Management (as of 30/6/2016)
  • Operational 3 years
  • 28 users in 9 roles and 24 groups
  • 2664 Items
  • 4 Application, 10 Workflows and 108 stages
  • 5471 total comments with 2073 system comments and 3398 user comments
  • 34 public filters and 69 private filters
  • 460 Attachments
  • Server Linux
  • Database DB2/400
  • Database Size 3800 MB
  • Gravity Directory Size 403MB


Customer Internal/External Project Management (as of 30/6/2016)
  • Operational 1 year
  • 316 users in 6 roles and 9 groups
  • 8412 Items
  • 3 Application, 11 Workflows and 81 stages
  • 9672 total comments with 1649 system comments and 8023 user comments
  • 140 Attachments
  • Server IBM i
  • Database DB2/400
  • Database Size 5400 MB
  • Gravity Directory Size 1300MB