Jump to: navigation, search

LFMT Storage and Resource Sizing

The following section describes how to size hardware for the LFMT Server Host(s). For information on storage requirements for the LFMT Client Host(s), please refer to the Genesys Administrator Extension (GAX) Deployment Guide.

Sizing Approach

LFMT sizing can be approached in two ways:

  • The Detailed Sizing procedure facilitated by the sizing table below will guide you to collect the information required to produce a strong estimate for your LFMT sizing needs. This will allow you to factor in your expected call volumes including peaks, your preferred log retention period, etc.
  • If a more expedient LFMT sizing is preferred, the Simplified sizing can provide a guide to get you started more quickly. However, please note:
    • These are approximate, and you may need to adjust your data retention period so that your log producing rate does not overfill the CLS central file storage.
    • It is recommended that you provision the hardware in a way that is easily extendable in the future so you can adjust it to your preferences. E.g. Perhaps your environment data generation rate only allows for 6 days of logs stored on the default proposed storage but your company prefers a longer period, then additional storage may need to be planned.

LFMT - Detailed Sizing Approach

Genesys recommends that the LFMT Indexer and LFMT Collector be installed on the same drive where the host Operating System resides. Minimum recommended storage for this drive is as follows:

  • 100GB for hosts running a Linux Operating System
  • 160GB for hosts running a Windows Operating System

An additional drive is recommended for housing the Central Log Storage (CLS). To calculate CLS storage requirements, download and refer to the Genesys Log File Management Tool Sizing Template.

Use the following table to estimate the Memory and CPU requirements for the LFMT Server Host(s). From the sizing template results, average throughput for log generation, or CLS storage requirements can be used as a reference.

Average Throughput CPU-Processor (Xeon-class 2.2 GHz or better) Memory CLS Storage*
Less than 2MB/s One quad-core processor 4GB to 8GB Up to 500GB
Between 2-10MB/s Two quad-core processors 8GB Up to 2.5TB
Between 10-25MB/s Three quad-core processors 16GB Up to 7.5TB
Between 25-50MB/s Four quad-core processors 16GB Up to 15TB
Greater than 50MB/s Please consult with Genesys Customer Care.

LFMT - Simplified Sizing Approach

Genesys recommends that the LFMT Indexer and LFMT Collector be installed on the same drive where the host Operating System resides. Minimum recommended storage for this drive is as follows:

  • 100GB for hosts running a Linux Operating System
  • 160GB for hosts running a Windows Operating System

An additional drive is recommended for housing the Central Log Storage (CLS). To calculate CLS storage requirements, refer to the table below.

Use the following table to estimate the Memory and CPU and storage requirements for the LFMT Server Host(s). Average daily call volume can be used as a reference. Note that a deployment would typically have a separate LFMT Server host per datacenter so the sizing should represent the call volume handled by that datacenter.

Average Daily Calls CPU-Processor (Xeon-class 2.2 GHz or better) Memory CLS Storage*
Less than 10k One quad-core processor 4GB to 8GB 200GB
Between 10k-30k Two quad-core processors 8GB 500GB
Between 30k-120k Three quad-core processors 16GB 2TB
Greater than 120k Please consult with Genesys Customer Care. (Detailed Sizing approach recommended)
Important
Storage is based on calculations for 7 days of log files and includes allowance for the operation of the application. When using the Simplified LFMT sizing method, we recommend you start by configuring a low log file retention period (e.g. 3 or 4 days) and then adjust it accordingly after data collection is started and it is clear there is sufficient space for additional retention.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 19 September 2017, at 11:05.