DNG is running slow
2 answers
Hi James,
https://jazz.net/wiki/bin/view/Deployment/MustgatherPerformanceProblemsInCLM is a good starting point for any performance problem in DNG.
The main question being what happened before DNG started to be noticeably slower, or was it also so? DNG has its main index on the file system and if your system is large than ensuring that this Jena index is in RAM is important.
However, as Donald says, this is usually a complicated question and more appropriate for a PMR. Here is a quick checklist on top of the must gather:
1) Are you seeing swapping on your system & does the memory on the system match: The_silver_bullet_of_using_Java
2) Are you experiencing java cores and what are they saying
3) Are you using Oracle, SQL Server or DB2? Have you run dbstats recently?
4) Did you upgrade recently? IF so, start here: Upgrade Must Read List, especially https://jazz.net/library/article/1516#00111
5) Monitor_your_way_to_good_Java_health really is the key here.
If you raise a PMR, apart from any product logs, we'd always ask for verbosegc output and also any indicators of system performance you have to ensure the most obvious bottlenecks are not being hit
IF you have specific use cases which are slow then that might be easier.
IF you have a lot of projects, then you might be hitting this: Tuning the configuration cache for DOORS Next Generation
As you can see. There are a lot of ifs in this reply. I hope that one of them gives you a good starting point, but I would highly recommend using this information as a starting point for a PMR/SR with Support.
https://jazz.net/wiki/bin/view/Deployment/MustgatherPerformanceProblemsInCLM is a good starting point for any performance problem in DNG.
The main question being what happened before DNG started to be noticeably slower, or was it also so? DNG has its main index on the file system and if your system is large than ensuring that this Jena index is in RAM is important.
However, as Donald says, this is usually a complicated question and more appropriate for a PMR. Here is a quick checklist on top of the must gather:
1) Are you seeing swapping on your system & does the memory on the system match: The_silver_bullet_of_using_Java
2) Are you experiencing java cores and what are they saying
3) Are you using Oracle, SQL Server or DB2? Have you run dbstats recently?
4) Did you upgrade recently? IF so, start here: Upgrade Must Read List, especially https://jazz.net/library/article/1516#00111
5) Monitor_your_way_to_good_Java_health really is the key here.
If you raise a PMR, apart from any product logs, we'd always ask for verbosegc output and also any indicators of system performance you have to ensure the most obvious bottlenecks are not being hit
IF you have specific use cases which are slow then that might be easier.
IF you have a lot of projects, then you might be hitting this: Tuning the configuration cache for DOORS Next Generation
As you can see. There are a lot of ifs in this reply. I hope that one of them gives you a good starting point, but I would highly recommend using this information as a starting point for a PMR/SR with Support.
Hello James,
Not sure what version you're using, but there is a known performance issue in with 6.x. The issue is documented in the following technote. The first thing to check is to make sure the database statistics are up to date. And depending on the database vendor, check the technote to see if there are additional steps needed for that particular database vendor.
Performance issues and CRRRW7556E after upgrading repository
I hope this helps.
Not sure what version you're using, but there is a known performance issue in with 6.x. The issue is documented in the following technote. The first thing to check is to make sure the database statistics are up to date. And depending on the database vendor, check the technote to see if there are additional steps needed for that particular database vendor.
Performance issues and CRRRW7556E after upgrading repository
I hope this helps.
Comments
We have been experiencing those issues after an upgrade, but that guide was followed to no avail. There is a critical PMR open right now to resolve these issues. Just letting OP know, follow the support doc Erica posted and try to increase/tune your server resources, but there may be some deeper performance issues with 6.0.2 ifix006 right now that are being worked out.
Comments
Donald Nong
Dec 12 '16, 8:16 p.m.CPU and memory usage is usually the first thing you need to check. Beyond that, it is too complicated for a few words in the forum.