cristimitulescu
Technical User
Hi,
We have a fairly large 9.7.1 system and we seem to be adding more content at times then the current Enterprise dataflow can process.
I have created multiple document converter processes, multiple index engines, have spread processes across multiple servers, use dedicated relatively high end NetApp NAS for the ipool location and index partitions but still fail to stay on top of it at times.
The bottleneck seems to be the Update Distributor. I don't believe you can have multiple Update Distributors and not sure that the Update Distributor can be multithreaded. The servers where the Update Distributor and index partitions are hosted do not have CPU or memory issues, the latency of the index volumes on the NetApp is very low averaging 1.5ms(fair amount of ssd cache) so for the life of me I don't see why we get big queues of pending messages at the update distributor.
I am now trying to explore the possibility of creating a second Dataflow and assign it either an existing branch of the folder/tree structure or create a new tree under the Enterprise and assign it to the new Dataflow.
However I haven't come across much information on how you set this up. Does anyone have documentation or experience with multiple dataflows?
Thank you,
Cristi
We have a fairly large 9.7.1 system and we seem to be adding more content at times then the current Enterprise dataflow can process.
I have created multiple document converter processes, multiple index engines, have spread processes across multiple servers, use dedicated relatively high end NetApp NAS for the ipool location and index partitions but still fail to stay on top of it at times.
The bottleneck seems to be the Update Distributor. I don't believe you can have multiple Update Distributors and not sure that the Update Distributor can be multithreaded. The servers where the Update Distributor and index partitions are hosted do not have CPU or memory issues, the latency of the index volumes on the NetApp is very low averaging 1.5ms(fair amount of ssd cache) so for the life of me I don't see why we get big queues of pending messages at the update distributor.
I am now trying to explore the possibility of creating a second Dataflow and assign it either an existing branch of the folder/tree structure or create a new tree under the Enterprise and assign it to the new Dataflow.
However I haven't come across much information on how you set this up. Does anyone have documentation or experience with multiple dataflows?
Thank you,
Cristi