Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
📖 Home Back
A new form of logging to investigate performance issues exists which is more useable than 'LCK logging' in DB_XXX logs. This is from ClearSCADA 2015 R1. It is visible in the ServerStatus client and DBSnapshot logs. It provides summary information on Read and Write lock usage in the system but does not have the logging overhead of 'LCK logging' (which produces log entries for every request, acquisition and freeing of a lock)
This 'Read/Write Lock Diagnostic' logging is enabled in ServerStatus :
ServerStatus_ReadWriteLockDiagnostics_001.pngServerStatus_ReadWriteLockDiagnostics_001.png
In addition, it is possible to reset accumulated snapshot values after each snapshot is reported. This affects many sections of the snapshot, not just this 'Read Write Lock Diagnostics' section. However, resetting the accumulated/maximum values after each snapshot can be very useful, even if applied and then removed for a few snapshots.
Snapshot_ResetAccumulatedValues_False.JPGSnapshot_ResetAccumulatedValues_False.JPG
Go: Home Back
A new form of logging to investigate performance issues exists which is more useable than 'LCK logging' in DB_XXX logs. This is from ClearSCADA 2015 R1. It is visible in the ServerStatus client and DBSnapshot logs. It provides summary information on Read and Write lock usage in the system but does not have the logging overhead of 'LCK logging' (which produces log entries for every request, acquisition and freeing of a lock)
This 'Read/Write Lock Diagnostic' logging is enabled in ServerStatus :
ServerStatus_ReadWriteLockDiagnostics_001.pngServerStatus_ReadWriteLockDiagnostics_001.pngIn addition, it is possible to reset accumulated snapshot values after each snapshot is reported. This affects many sections of the snapshot, not just this 'Read Write Lock Diagnostics' section. However, resetting the accumulated/maximum values after each snapshot can be very useful, even if applied and then removed for a few snapshots.
Snapshot_ResetAccumulatedValues_False.JPGSnapshot_ResetAccumulatedValues_False.JPG
DB\ResetCountersOnSnapshot=Trueto reset accumulated values/stats after each snapshot written to DBSnapshot logs.
Go: Home Back
Author
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.