[cisco-voip] Device Pool Updates

[Wes Sisk]

Additionally, "cpu goes to 100% on the server". Do you mean on the 
publisher or on a subscriber?  100% cpu isn't necessarily bad.  Which 
process is consuming the processor?  Any update at all results in work 
by SQL (or Informix), Aupair (or dbnotify), and affected processes ccm, 
cti, and ctftp.

IMHO 'device pools' are system wide objects and fit into the category of 
things that should not be approached casually.  Take for example:
http://puck.nether.net/pipermail/cisco-voip/2008-July/035735.html

Regards,
Wes


On Wednesday, February 04, 2009 5:19:15 PM, Scott Voll 
<svoll.voip at gmail.com> wrote:
> what version of CM?
>
> On Wed, Feb 4, 2009 at 2:06 PM, Michael Back <Michael.Back at nisd.net 
> <mailto:Michael.Back at nisd.net>> wrote:
>
>     I needed to change the CM group on several brand new device pools I
>     created.  None of the se device pools have any phones associated with
>     them.  Once I select update, CPU goes to 100% on the server.  Can
>     someone explain to me why a change to a device pool would cause
>     high CPU
>     utilization?
>
>     Thanks
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090204/9707409a/attachment.html>