Software Versions & Server Sizing

Software versions

The software versions currently used are:

 All of them have built it redundancy capabilities.

Server Sizing

This number should be taken only as a reference, the final sizing would be done during each project.

General assumptions:

  • 50 sensor points per location
  • Average 15 min interval
  • 500 users working parallel with web-gui
InstanceMemoryCPU CoresStorage
Small8 GB2100 GB
Medium16 GB4500 GB
Large32 GB82 TB

Tomcat Application Server

 For anything larger than 1000 sites we would recommend to separate data-processing server and Web-Interface server (tomcat).

Locations (up to)

Tomcat (data processing)

Tomcat (web interface)

Load Balancer

1000

Medium


3000

Medium

Medium

Small

5000

Medium

Medium

Small

10000

Large

Large

2x Medium

30000

2x Large

Large (500 users)

2x Medium

Sizing influences

Sensors, intervals

Web users


ActiveMQ

Locations (up to)

ActiveMQ

Comment

1000

Medium

(or 2x Small – reliability) 

3000

Medium

(or 2x Small – reliability)

5000

2x Medium (1Master 1 Slave)


10000

2x Large  (1Master 1 Slave)


30000

3x Large  (1Master 2 Slaves)


Sizing Influences:

  • number of sensors
  • polling interval

Databases

  • PostgreSQL (or any other SQL)
  • InfluxDB

Locations (up to)

Databases

Comment

1000

Medium

 

3000

Medium

 

5000

Large

(or 2x Medium – reliability)

10000

 1x Large 1x Medium

1 Cluster 1 Shard

30000

3x Large 

1 Cluster 2 Shard

Sizing influences:

  • number of sensors
  • polling interval
  • historical data persistance time

Storage and Bandwidth

Please refer to /wiki/spaces/SIT/pages/26542101 for further information.