r4 - 2016-09-28 - 13:10:48 - Main.d3v3r1ttYou are here: TWiki >  Deployment Web > DeploymentPlanningAndDesign > CLMSizingStrategy > CLMSizingStrategyComments
  • I think we need to add JRS and DCC to the mixe -- PhilippeChevalier - 2016-01-11 - 10:31
  • "If there is too much demand for memory, the operating system's file cache may shrink and this can impact the caching of index data used by CLM applications. This is especially true for DOORS Next Generation and the Lifecycle Query Engine."

When we write "cache" and "caching" here, I think the Linux terminology may actually be "buffer" and "buffering".

In the Kista support team right now, we have some discussions about how you can monitor the memory usage for indexing. Focusing on active memory or process memory consumption, will not show how the OS buffers indices in RAM to avoid disk i/o. -- ErikMats - 2016-03-16 - 05:56

  • Please add JRS sizing guide -- DianeEveritt - 2016-09-28 - 09:10
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.