Pro2-Why reducing thread polling interval to 2 seconds not a good practice


Article Number000093739
EnvironmentProduct: Progress
Product: OpenEdge
Version: All Supported Versions
OS: All Supported Platforms
Other: Pro2, Pro2SQL, Pro2ORA
Question/Problem Description
Why reducing thread polling interval to 2 seconds not a good practice
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
This setting only comes into play when a thread makes a full top to bottom pass on the queue records it processes.  Polling every two seconds simply means it restarts the process again very quickly.  While this might seem a good idea, during periods of low queue volumes the thread processes are constantly attempting to do reads and write logs. A typical value would be 60 sec sleep interval. if the table/rows in question are not moving quickly enough for this use-case, moving this table into a thread with no other tables might be a better practice, or into a thread with lower overall volume than the thread onto which it is currently assigned. Queue volume by thread is the main factor in events not being replicated in a timely fashion. If the table is in a thread to it's own, then volume lags are typically eliminated.
Last Modified Date1/10/2019 2:00 PM

Did this article resolve your question/issue?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025