query change notification
From: Jeff Chirco <backseatdba_at_gmail.com>
Date: Tue, 23 Feb 2021 09:18:25 -0800
Message-ID: <CAKsxbLrofru3=_iqtSdUcH6ypO1sdAo6f1+rCKMe2YaRxfKXVw_at_mail.gmail.com>
We have an application that might benefit from using query change notification. We are a restaurant company, each store has an application which displays information and refreshes every minute. Majority of the time the data has not changed and therefore CPU cycles are getting wasted. We have 400 locations so it contributes to a lot of wasted CPU in my mind. I want to purpose using query change notification in their .Net application but I am curious on the DBA side of things. Is there anything to consider about having 400 and growing change notification requests for the database to manage? I am assuming each store would have to register its own request.
Date: Tue, 23 Feb 2021 09:18:25 -0800
Message-ID: <CAKsxbLrofru3=_iqtSdUcH6ypO1sdAo6f1+rCKMe2YaRxfKXVw_at_mail.gmail.com>
We have an application that might benefit from using query change notification. We are a restaurant company, each store has an application which displays information and refreshes every minute. Majority of the time the data has not changed and therefore CPU cycles are getting wasted. We have 400 locations so it contributes to a lot of wasted CPU in my mind. I want to purpose using query change notification in their .Net application but I am curious on the DBA side of things. Is there anything to consider about having 400 and growing change notification requests for the database to manage? I am assuming each store would have to register its own request.
Any thoughts?
Thanks,
Jeff
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Feb 23 2021 - 18:18:25 CET