Hello folks

 

I wanted to ask a few questions around The Provider and its usage if I may
please.

 

I have a customer with a CAS and 2 PRI sites.  They have quite a complex RBA
model.  They do all management against the CAS.

 

They have 458 installed copies of the CM console and they have a fair number
of administrators.

 

Previously they had a single provider and were experiencing crashes on a
fairly regular basis.

 

Things that we have done to try and alleviate this issue:

 

-        We have increased the memory and threads that the provider can use.
This helped a little

-        We have introduced a second provider and again this has helped
some.  The main issue with the provider on the CAS still exists.

 

We could of course introduce a third provider and this might help but now we
are in the position where in essence we are stabbing in the dark - there
don't appear to be any good ways to get metrics on concurrent connections or
loading on the provider itself.  The only suggestion that I can make is to
run the provider in its own process and to monitor this.

 

Other things that I want to look at are to reduce the number of consoles
which are deployed in the estate.  There are a fair number of users who are
on support and they really just use remote control.  I know that this still
does make provider connections, but only to check permissions for the user
running it - does anyone have a handle upon how much less intensive this is
than calling from the console?

 

There is a project to implement SCorCH within the organisation and we'll
look to moving some of the workloads into this at some point but does anyone
have any additional ideas?

 

Thanks

 

Jason



Reply via email to