Snapshot_EventQueueSize without current values

Hello User16879481478033348026,

I am used to @mention but the platform appears to not knowing your nickname (User16879481478033348026) and I guess you may have changed it meanwhile.

Tuning Parameters are not excessively documented. We recommend sticking with the defaults (what's applied by the setup) unless you run into any issues and Technical Support staff, after analyzing the issue(s) you are facing, is asking you to change a certain setting.

PI System Management Tools (PI SMT) is the PI admins tool for the purpose and the Tuning Parameter add-in also shows explanations, at least for some of the Tuning Parameters. When the Tuning parameter shows empty (no value), the default is used, as you already assumed. What the default is should be part of the Tuning Parameters explanation.

Archive_AutoArchiveFileSize is used when the current Primary archive fills up and a new archive file needs to be created with the aim to shift into it as the new Primary archive.

The PI Data Archive has a memory mapped Event Queue between the Snapshot and the Archive subsystem. In case the PI Data Archive is busy or otherwise experiencing an issue, the memory mapped Event Queue is preventing against data loss. PI Snapshot Subsystem is writing to this memory mapped queue and if the current queue file is full, a new queue file will be created with its size being defined by the Snapshot_EventQueueSize parameter. Under normal operation, there should be only a single event queue file or with other words, if there is more than one event queue files, this usually already indicates an issue. While heavy load may be just temporary, a growing amount of Event Queue files can be considered a clear indication that the PI Archive Subsystem isn't able to keep up.

Again, the default values of Tuning Parameters usually work for the majority of PI System installations. Should you have doubts or your PI Data Archive is experiencing issues, please log a ticket with the PI Support at AVEVA.

Hello User16879481478033348026,

I am used to @mention but the platform appears to not knowing your nickname (User16879481478033348026) and I guess you may have changed it meanwhile.

Tuning Parameters are not excessively documented. We recommend sticking with the defaults (what's applied by the setup) unless you run into any issues and Technical Support staff, after analyzing the issue(s) you are facing, is asking you to change a certain setting.

PI System Management Tools (PI SMT) is the PI admins tool for the purpose and the Tuning Parameter add-in also shows explanations, at least for some of the Tuning Parameters. When the Tuning parameter shows empty (no value), the default is used, as you already assumed. What the default is should be part of the Tuning Parameters explanation.

Archive_AutoArchiveFileSize is used when the current Primary archive fills up and a new archive file needs to be created with the aim to shift into it as the new Primary archive.

The PI Data Archive has a memory mapped Event Queue between the Snapshot and the Archive subsystem. In case the PI Data Archive is busy or otherwise experiencing an issue, the memory mapped Event Queue is preventing against data loss. PI Snapshot Subsystem is writing to this memory mapped queue and if the current queue file is full, a new queue file will be created with its size being defined by the Snapshot_EventQueueSize parameter. Under normal operation, there should be only a single event queue file or with other words, if there is more than one event queue files, this usually already indicates an issue. While heavy load may be just temporary, a growing amount of Event Queue files can be considered a clear indication that the PI Archive Subsystem isn't able to keep up.

Again, the default values of Tuning Parameters usually work for the majority of PI System installations. Should you have doubts or your PI Data Archive is experiencing issues, please log a ticket with the PI Support at AVEVA.

Thanks for the response, yes my username is an issue I havent been able to resolve yet…it doesnt let me change it, but yes, thanks again for the response, I will notify the client that these parameters should remain default, as far as today we have no issues that ask for changes in this area. I will monitor the system in case something shows up.