Otherwise reads/writes are throttled dynamically based on current system performance - e.g. calls, admin tasks, other applications using AXL, etc. Applications should be prepared to handle requests failing with a throttle error, and be able to sanely reschedule/retry/back-off requests to work through resource constrained situations.
The number of updates/min will certainly depend on the type of operation and its impact on the data-size, number of DB tables/rows affected, and any resulting notifications/operations needed by the real-time components of CUCM.
Can you elaborate on the use-case for performing this level of updates..?
Usually i wait for a reply to my response so i know cucm has processed my request. Sometimes i found tomcat to struggle if i sent to many request in a short amount of time. I then add a short break every 500-1000 requests which works fine for me
Welcome!To my Webex Developer resource overview
Like it?Please scroll to the end and click the 'Helpful' button!
Contribute?Something I should add? Let me know in the comments!
QUICK ACCESS TO THIS PAGE: cs.co/webexdevinfo  ...
The browser-based Finesse Agent Desktop 12.5, that ships with the Cisco Unified CCE / CCX contact center solutions, has made massive strides in the performance of its underlying infrastructure, which improves its throughput and reliability ...
Fun and Easy Virtual Hackathon
60 Teams Win Prizes
ALL Participants Receive Certificate Signed by Execs
Important Note: This contest is governed by the Terms and Conditions in the document attached at the end of this page. Please re...
Hi Experts, I Need one help on Cisco social miner , hope you will help us on below requirements . Many Thanks!!!!Actually, we have third party application trying to integrate in UCCE through task routing API concept .Just we need to get the agen...