在 MarkLogic 中设置最大森林大小的任何参数？
Any parameter to set max forest size in MarkLogic?
是否有任何参数可以控制森林的最大大小？
或任何最佳实践，正在运行的脚本？
森林大小没有硬性限制，但有一些通用准则。文档的大小和类型、索引、硬件规格和使用模式等因素都会影响性能。
来自 MarkLogic 第 3 章的指导 Scalability, Availability, and Failover Guide：
Forest Sizes Per Data Node Host
As your content grows in size, you might need to add forests to your database. There is no limit to the number of forests in a database, but there are some guidelines for individual forest sizes where, if the guidelines are greatly exceeded, then you might see performance degradation.
The numbers in these guidelines are not exact, and they can vary considerably based on the content. Rather, they are approximate, rule-of-thumb sizes. These numbers are based on average sized fragments of 10k to 100k. If your fragments are much larger on average, or if you have a lot of large binary documents, then the forests can probably be larger before running into any performance degradation.
The rule-of-thumb maximum size for a forest is 512GB. Each forest should ideally have two vCPUs of processing power available on its host, with 8GB memory per vCPU. For example, a host with eight vCPUs and 64GB memory can manage four 512GB forests. For bare-metal systems, a hardware thread (hyperthread), is equivalent to a vCPU. It is a good idea to run performance tests with your own workload and content. If you have many configured indexes you may need more memory. Memory requirements may also increase over time as projects evolve and forests grow with more content and more indexes.
是否有任何参数可以控制森林的最大大小？ 或任何最佳实践，正在运行的脚本？
森林大小没有硬性限制，但有一些通用准则。文档的大小和类型、索引、硬件规格和使用模式等因素都会影响性能。
来自 MarkLogic 第 3 章的指导 Scalability, Availability, and Failover Guide：
Forest Sizes Per Data Node Host
As your content grows in size, you might need to add forests to your database. There is no limit to the number of forests in a database, but there are some guidelines for individual forest sizes where, if the guidelines are greatly exceeded, then you might see performance degradation.
The numbers in these guidelines are not exact, and they can vary considerably based on the content. Rather, they are approximate, rule-of-thumb sizes. These numbers are based on average sized fragments of 10k to 100k. If your fragments are much larger on average, or if you have a lot of large binary documents, then the forests can probably be larger before running into any performance degradation.
The rule-of-thumb maximum size for a forest is 512GB. Each forest should ideally have two vCPUs of processing power available on its host, with 8GB memory per vCPU. For example, a host with eight vCPUs and 64GB memory can manage four 512GB forests. For bare-metal systems, a hardware thread (hyperthread), is equivalent to a vCPU. It is a good idea to run performance tests with your own workload and content. If you have many configured indexes you may need more memory. Memory requirements may also increase over time as projects evolve and forests grow with more content and more indexes.