-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Further improvement of Performance #1544
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1544 +/- ##
==========================================
+ Coverage 70.78% 70.80% +0.02%
==========================================
Files 121 121
Lines 4970 4988 +18
==========================================
+ Hits 3518 3532 +14
- Misses 1452 1456 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Looks good to me, Thanks. It is certainly better to read those informations only once. Regarding the overall performance see my notes in #1508 |
@voisardf @kdeininger @michmuel I would be happy to see a quick review on that too :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I deployed the branch in our test setting. Seems to work smoothly. Thanks.
@peterschaer
I did a quick profile of the extract generation (based on our small test data set). It reveals several points to poke around. But one easy catch is right in the beginning of the process:
Is related to #1508
As you can see we lose almost 4% of process time between start and ExtractReder.read, I found that we had an old left over in the code. Instead of reading glossaries, disclaimers and municipalities for every extract they are read once on server start now.
Could you please try and tell what you think about this?
To use this patch it should be enough to install it. No config changes needed.