Reminder! Until the end of the month, our Learning Track over Advanced Normalization is unlocked and available to all Grooper xChange users!
Grooper 2.80.0043 is now available! Check the  Downloads Discussion for the release notes and to get the latest version.
Grooper 2.90.0051 is now available! Check the  Downloads Discussion  for the release notes and to get the latest version.

Speed troubleshooting

What is the best way for us to figure out what is making the Extract step in a process take so long?  The first thing that comes to mind is to go extractor-by-extractor and see which ones takes so long. So we did that, but the extraction step for a single doc is taking significantly longer than the sum of all the extractors one-by-one.
Kyle Souza
Data Wizard
P&P Oil & Gas Solutions

Best Answer

  • GrooperGuruGrooperGuru Posts: 465 admin
    Accepted Answer
    Definitely need to use the information in the instance viewer to troubleshoot performance. Go to your data model, then visit the extraction tester tab. Open a document to review there. In the review screen, re-run extraction on a document, then switch to the instance viewer. In that viewer, it will report the time to extract (in MS) by data element. This will quickly help you narrow down the slowest parts of the model.
    Matt Harrison
    Director of Strategy
    [email protected]

Answers

  • dearnerdearner Posts: 253 admin
    pinging @GrooperGuru on this one; there's a lot you can do using the instance viewer to troubleshoot extraction speed
Sign In or Register to comment.