SonarG 4.1

System Sizing

A single SonarG node is usually used for up to 30TB of compressed Guardium data. You can store more than 30TB on a single node and reporting times may still be reasonable but you can also cluster multiple SonarG nodes to provide faster response times. Consult your account manager for additional sizing guidelines.

Each SonarG node should have the following specs:

  • Two Intel Xeon processors, at least 6 cores per socket, at least 2.4Ghz each.

  • At least 64GB of memory.

  • Either HDD or SSD drives. In both cases, and especially when using HDDs, the drives should be striped using RAID0 or RAID10. For example, you can choose to use SATA drives. In this case you should create a single RAID array using at least four such disks to give you the ability to read at a rate nearing 500MB/s. The system has been optimized to allow leveraging low-cost SATA drives in order to achieve the most cost-effective large data store using inexpensive drives.

  • At least one SSD of size ~400MB used for temp storage for SonarW.

If you are deploying SonarG on an Amazon AWS EC2 instance, SonarG recommends using a m4.4xlarge instance or an m4.10xlarge instance if workloads are expected to be very large. An io2 EBS volume with at least 10K-12K PIOPS is recommended since this will allow you to grow the volume as your data size grows with no changes to the SonarG application or to RHEL. If you choose general purpose EBS then you should use a RAID0 configuration.

When using virtual machines (VMs), the recommended minimum production configuration is 8 vCPUs and 64GB RAM. You must work with your VM administrator to provision enough IOPS dependant on your loads and data volumes. A VM machine with 32GB RAM and 6 vCPUs can be used for a POC host, with the understanding that the performance will not be optimal.

If you are deploying SonarG on a machine that has between 96GB to 128GB of RAM, set the parameter block_allocation_size_percentage to 33. This will take advantage of the memory available. If you are deploying on a machine that has 128GB of RAM or more, set block_allocation_size_percentage to 50.