Performance issues faced in DNG:Opening a view that shows all the Terms with some links and attributes included often results in error messages
Dear All,
I am facing the following error message while opening a module for the particular view.
Use case:
Opening a view inside the module that shows all the Terms with some links and attributes included often results in error messages like:
The list of artifacts cannot be displayed.
hide details
ID CRRRW7611W The server was unable to generate the list of artifacts in a reasonable period of time. Try making the filter more specific. For example, specify which artifact types to display, and try to open the list again.
In general listing more than ˜100 Artefacts is taking a very long time."
Can any one please describe why it is being displayed and how it can be resolved??
Thanks.
I am facing the following error message while opening a module for the particular view.
Use case:
Opening a view inside the module that shows all the Terms with some links and attributes included often results in error messages like:
The list of artifacts cannot be displayed.
hide details
ID CRRRW7611W The server was unable to generate the list of artifacts in a reasonable period of time. Try making the filter more specific. For example, specify which artifact types to display, and try to open the list again.
In general listing more than ˜100 Artefacts is taking a very long time."
Can any one please describe why it is being displayed and how it can be resolved??
Thanks.
One answer
Shiraam,
Performance issues can be very complex to troubleshoot as there could be a number of contributing factors. The error you are showing simply says, the query timed out. The quick fix to this would be to increase the query timeout value in the advanced properties of the rdng admin page.
Some questions you may consider?
1) is this a change in behavior? (Did the page used to load without issue)
1) is this a change in behavior? (Did the page used to load without issue)
This could indicate that our repository is getting very large.
2) What version of RDNG are you using.
The newer versions have significant performance improvements.
3) What are you querying?
Certain components / queries take longer to load.
4) What are your system resources looking like?
RDNG, unlike other CLM tools is very (very) index dependent. Best practices would dictate that you have enough system memory available (after the JVM memory, after the OS memory,..etc) left over to contain your RDNG index completely. Consider this:
JVM max heap + OS memory (depends on OS and other processes running) + RDNG index size = total available memory.
JVM max heap + OS memory (depends on OS and other processes running) + RDNG index size = total available memory.
Here is a great article on RDNG performance: https://jazz.net/wiki/bin/view/Deployment/SizingAndTuningGuideForRationalDOORSNextGenerationVersion50
The article clearly explains the relationship between memory, disk type, disk speed, artifact count,..etc.
As I noted earlier. Performance is a complex issue to troubleshoot but this should get you going.
Good luck,
Mike