Test system specifications
- Last UpdatedApr 24, 2025
- 1 minute read
The system on which the testing was performed had the following specifications.
|
Item |
Specification |
|---|---|
|
Size of the TimeSeries database |
819 GB |
|
Space available in the TimeSeries database |
325 GB |
|
Number of rows in TimeSeries Collect |
>725 Million |
|
Number of collect rows per tag (for the test points used) |
7100 – 7600 (average of 7300) |
|
Clustered? |
Yes |
|
Number of cores on the computer |
8 |
|
Configured for partitioning |
No |
|
Everything on one physical disk |
No. TimeSeries log and data are on separate disks. |
In order to remove issues caused by fragmentation, a full rebuild of the collect, tag, and dataQualityDefine indices was performed prior to running any tests. A reboot of the server was also performed before each batch of tests was run in order to remove any pre-caching of information.
It is important to note that Elk SP4 Historical-Historical Hotfix 7.7.1.4 was in place at the time of testing. In this hotfix, changes were made to the readTimeSeriesCollect Historical procedure to improve the performance of TimeSeries trends. This was accomplished by replacing embedded scalar function calls to getDQName with joins between the collect table and the dataQuality table. This hotfix would only affect reading from the TimeSeries Collect table, and would not affect test results for insert and delete operations.