Rockwell Automation FactoryTalk Historian Classic for Batch User Guide - Manual (Page 27)

Configuring FactoryTalk Historian for Batch Chapter 2
• Batch Archiver for Batch Server1 should be started at 1
minute past the hour.
• Batch Archiver for Batch Server2 should be started at 4
minutes past the hour.
• Batch Archiver for Batch Server3 should be started at 8
minutes past the hour.
BatchArchiver1 will run at x minutes
past the hour:
1 11 21 31 41 51
BatchArchiver2 will run at x minutes
past the hour:
4 14 24 34 44 54
BatchArchiver3 will run at x minutes
past the hour:
8 18 28 38 48 58
These settings allow each Archiver to run for approximately 3
minutes by itself and will reduce the likelihood of more than one
Archiver sending data to the FactoryTalk Historian for Batch
database server at the same time. FactoryTalk Historian for Batch
performance is primarily dependent on the hardware and memory in
the computer used for the database server. In a typical desktop-class
machine, FactoryTalk Historian for Batch functionality can parse,
transform, and store event record data at a rate of approximately 300
event records per second. This means that if the Batch Archiver for a
particular batch server sends less than 54000 event records to the
FactoryTalk Historian for Batch database server (every time it
incrementally runs), the database server will never be required to
process data from more than one Archiver at a time. This balances
the load.
NOTE
The following recommendations are optional but strongly suggested
when running FactoryTalk Historian for Batch in a multiple batch server
environment.
Minimizing the number of events that are archived reduces the load
on the FactoryTalk Historian for Batch database server. Minimizing
the number of event filters that are selected reduces the event data
Event Filter
Recommendations For
Multiple Batch Server
Environments
Rockwell Automation Publication BHIST-UM011A-EN-E-June 2014 27