Knowledge Discovery 25.1
Knowledge Discovery Expert

# Scale Agentstore and Utility Content components

The previous sections have discussed the sizing and scaling of a distributed Content component index. However, you can also deploy Content in situations that do not have a large associated index, for example as an Agentstore (when the number of documents, and the documents themselves, tend to be smaller), or for performing utility functions, such as language detection, document statistics, or highlighting.

In these circumstances, it is not generally necessary to distribute documents, but you might need to distribute queries using a single DAH in mirror mode. You can use a single DIH, also in mirror mode to keep the contents of the child servers (for example agents) in sync. In this case, you can scale the system by assessing the throughput of a single Agentstore, again most practically by realistic small-scale testing.

If multiple parallel processes might use the child servers (for example, multiple instances of CFS run on several machines), it might make sense not to route all queries through a top-level DAH. In this case, you might instead want to connect each CFS or other component to a local Agentstore component or utility Knowledge Discovery running on the same machine.

Copyright 2024 Open Text
Version 25.1 | Last updated January 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery 25.1

Topic Title: Scale Agentstore and Utility Content components