- Running it in a Docker container, or
- Running as a setup file
If you are getting started with PARME Compliance Box, we recommend running PARME Compliance Box as a Docker container since Docker contains the external dependencies needed.
For information on how to choose hardware, and how to size your PARME Compliance Box box installation, please contact us.
Hardware requirements depend on – how much data you will be ingesting, and – how many concurrent accesses you will be running
Scaling Your Environment
PARME Compliance was made to scale, and scales very well within the nodes in a cluster. Running a cluster of three or more PARME Compliance nodes provides higher capacity in terms of both ingest and access performance, and also allows high availability by replicating data to more than one node. In fact, replication depends a lot on the database you select as all the data is stored on a SQL database.
If you want to run a clustered node please review Cluster Setup.
When you design a PARME database, you may have to estimate how large the database will be when filled with data. Estimating the size of the database can help you determine the hardware configuration you will require to do the following:
- Achieve the performance required PARME Compliance Box.
- Guarantee the appropriate physical amount of disk space required to store the data and indexes.
Estimating the size of a database can also help you determine whether the database design needs refining. For example, you may determine that the estimated size of the database is too large to implement in your organization and that more normalization is required. Conversely, the estimated size may be smaller than expected. This would allow you to denormalize the database to improve query performance.
To estimate the size of a database, estimate the size of each data individually (user’s data, user’s activity log, user’s rights) and then add the values obtained. The size of a table depends on whether the table has indexes and, if they do, what type of indexes. In te real world the user’s activity logs are the most data consuming. The consumtion depends also on the number the data sources and the frequency and volume of data they store in PARME Database.
- Assume user’s data to injest come from PARME Core and 10 other sources and compression is activated for it. Test your database installation; better compression means better performance.
- You need to be able to hold 48 hours of compressed data in 80% of your RAM.
- You want enough hyper-threads/vCPUs (each giving you 1GB/s search) to be able to search 24 hours of data in less than 10 seconds.
- You need disk space to hold your compressed data. Never fill your disk more than 80%.
Example Setup Your machine has 32GB of RAM, 8 hyper-threads (4 cores) and 1TB of storage. Your machine can hold 460GB of ingest data compressed in RAM and process 8GB/s. In this case, it means 10 seconds worth of query time will run through 80GB of data. So this machine fits an 80GB/day ingest, with +5 days’ data available for fast querying. You can store 7.2TB of data before your disk is 80% full, corresponding to 90 days at 80GB/day ingest rate.
This example assumes that all data has the same retention settings. But you can configure PARME Compliance Box to automatically delete some events before others, allowing some data to be kept for several years while other data gets deleted after one week, for example.
For more details, please contact us. We will be very happy to help you in your sizing process.
Please refer to the administration reference page.