EBO Values' discovery takes long time

[mike_meirovitz]

Hi,

We have a Discovery processor that discovers all values in the EBO and attached remote controllers. One of our customers has 30,000 defined values in 30 remote controllers.

It takes 9 hours for the Discovery processor to complete which is very long time.

We consider breaking the Discovery processor to 30 Discovery processor, one for each controllers. This way, the customer will be able to only start the processor where there are changes and not to wait again for 9 hours.

My questions are:

1. Is there a limit of the number of processors we can define?

2. Does the processors' names must be unique?

3. Can we set the 'Start Search At Root Container Item' as hidden field with a predefined value 'False' in our Discovery processor settings?

4. Can we enforce the user to define at least one item in "Folder to Scan" in our Discovery processor settings? 

Thank you.

Mike

[JeffBowman · Accepted solution]

Hi Michael,

In general I wouldn't recommend configuring 30 instances of the same processor just for a discovery as just this configuration of this alone will be time consuming!

If you are experiencing this level of slowness you may want to take a look at what the root cause of this is, as creating 30 processors, and hope they run in parallel may not work as you hope.

But to your questions:

1. Not hard coded, but if you want to run all 30 at once, you will need to increase the number of Worker Threads in the settings.

2. No the names do not need to be unique.

3. This is possible, take a look at the 'VisibleWhenAttribute' in chapter 9.4.8 of the Developers Guide

4. This is possible, take a look at the 'CollectionLengthAttribute' in chapter 9.4.1 Developers Guide.

Best Regards,

-Jeff

[mike_meirovitz]

Hi Jeff,

Thank you. Understood.

Mike