Specifications

Call Detail Record Reports
C – 10 ShoreTel, Inc.
Performance Tuning for Report Generation
To improve on the CDR report generation performance, increase
INNODB_BUFFER_POOL_SIZE defined in c:\windows\my.ini based as specified
Default setting:
• INNODB_BUFFER_POOL_SIZE = 150 MB
If the database contains more than 350,000 records, set
• INNODB_BUFFER_POOL_SIZE = 200 MB
If the database contains more than 500,000 records, set
• INNODB_BUFFER_POOL_SIZE = 250 MB
Report generation time – CPU Utilization
Based on the size of the data requested for the report, the display time for the last page
of the report from the first page may require ten minutes. Even though the priority of
Report Generation process is set to below normal, generating large reports may
potentially impact the call processing performance. To avoid performance degradation
issues, do not generate large CDR reports during peak call loads.
MySQL CDR Database and Internationalization
MySQL CDR Database supports the UTF-8 character set. All CDR data in the database
is stored in UTF-8 character set.
Monitor MySQL service
To monitor and, when necessary, restart the MySQL service from ShoreWare Director,
access the Services page by selecting Maintenance | Services in the menu panel, then
select MySQL in the table on the Services page.
Tools for browsing MySQL database tables
MySQL provides MySQL Query Browser as part of their GUI Tools (http://
dev.mysql.com/downloads/gui-tools/5.0.html). MySQL Query Browser can be used to
browse and view the queries. The open source tool (http://www.webyog.com/en/
downloads.php) is available to view the CDR tables defined in MySQL.
Browsing a large CDR database on the Main server may potentially degrade the call
processing server.
Large amount of temporary disk space may be used by these MySQL browser tools. To
avoid affecting call processing performance on HQ, a query with LIMIT criteria can be
used to show a subset of rows.
Restrictions in the number of records returned by the MySQL CDR query
CDR database queries that exceed 300,000 records may cause performance degradation
when generating certain reports, such as Trunk Activity Detail and Trunk Activity
Summary. Increasing the amount of free disk space may mitigate this problem, as will
modifying the query filter to reduce the number of records returned by the query to
under 300,000.