AVID MEDIA INDEXER 3.7.1 TUNED PARAMETERS INFORMATION SET
Overview:
The memory and cpu use have been reported to be excessive to the point where external monitor tools are flagging the hosts are being out of house standards. The two items below are
intended to address those concerns and the result in a more responsive operation under all loading conditions. Item one is a limitation set for the mongod database service that is a part of the
Format Independence component of Interplay Multi Resolution media support. The field and lab stress testing have shown the used memory going in excess of 15 Gigabytes for this service. The
second component is a reduction in the Process Affinity for the AvidMI and Mongod executable processes. At this time a manual “disable” is required but this will be attended in in another
manner going forward.
Mongod memory use change:
The instructions below set the memory use to be limited to 9 Gigabytes for the Mongod database service on the Avid Media Indexer service hosts set to scan the shared storage media file
locations.
Actions:





stop MI service
stop Mongo service
delete file AvidMI/state/config/mongod.config
edit file AvidMI/state/config/mongod.config.tpl
Merge the following setting into the file at the appropriate section and use the number of GB of memory that mongo should be allowed to use, e.g. to limit at half of the default at a
32 GB machine, use 9
storage:
wiredTiger:
engineConfig:
cacheSizeGB: 9
-Continued on the next page-
Example End Result for the file’s content after the addition of memory limiting has been applied:
# Copyright 2016 by Avid Technology, Inc.
storage:
dbPath: ${env.MI_MONGODB_APPDATA_DIR}/mongodb-data
directoryPerDB: true
journal:
enabled: true
wiredTiger:
engineConfig:
cacheSizeGB: 9
systemLog:
destination: file
path: ${env.MI_MONGODB_APPDATA_DIR}/mongodb-log/mongodb.log
logAppend: true
timeStampFormat: iso8601-utc
net:
bindIp: 127.0.0.1
port: 27017
processManagement:
windowsService:
serviceName: Avid Interplay Media Indexer MongoDB
displayName: Avid Interplay Media Indexer MongoDB
Actions continued:

start MI service
**Note that MI will restart the mongo service by applying the mongod.config.tpl configuration as the new mongod.config configuration.
Over time to monitor either the Resource Monitor or Task manager to see that the application of the mongod memory limit has been placed into effect.
Reduction of the CPU’s associated with AvidMI.exe and Mongod.exe processing (Change Affinity)

From the Task Manager Processes tab with the check box for Show processes from all users set, locate and right click on the mongod.exe Image Name line. That will open a menu
where you can select the Set Affinity... option (see the image below).

From the resultant Process Affinity panel, scroll to the bottom of the list and deselect the last two items listed (note- your CPU designation may appear slightly different with Node 0
and Node 1 labels).


Once the deselection has been completed press OK to set and exit from the setting panel.
Repeat the process for the AvidMI.exe Image Name item
Note: These settings applications will only be persistent while the service stays running and a service or host restart will revert to processor affinity being set of all of the available CPU listed
instances. We hope to have a non user intervention process in the near term to remove this manual process.