Skip to content
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

change-legend-entries-retrieval #2050

Merged
merged 4 commits into from
Oct 17, 2024
Merged

Conversation

michmuel
Copy link
Collaborator

@michmuel michmuel commented Sep 3, 2024

No description provided.

@michmuel michmuel requested a review from svamaa September 3, 2024 14:16
@michmuel michmuel self-assigned this Sep 3, 2024
Copy link
Collaborator

@svamaa svamaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @michmuel for this PR!
I prefer this solution to the other PR.
However, I could neither measure any performance win within the standart pyramid_oereb example nor within our environment in BS. Did your extracts improve in BL?

@michmuel
Copy link
Collaborator Author

michmuel commented Sep 5, 2024

@svamaa The request for the xml-extract for egrid CH958382784904 (large real estate) seems to be faster by about 1s (10s to 9s in total).

@svamaa
Copy link
Collaborator

svamaa commented Sep 5, 2024

Good to hear, could we get any more tests from @voisardf @peterschaer @lopo977 ?

@lopo977
Copy link
Collaborator

lopo977 commented Sep 5, 2024

Good to hear, could we get any more tests from @voisardf @peterschaer @lopo977 ?

I just tried this branch with a 32-page extract, and here in Tessin, we see less than a 5% difference. However this branch seems also little faster.

@peterschaer
Copy link
Collaborator

I made a few measurements with complex extracts (large parcel, many legend items). Unfortunately, I could not observe any improvement in performance.

@michmuel
Copy link
Collaborator Author

The case where performance could be improved is limited to real estates that are covered by public law restrictions with law status "inKraft" AND "laufende Aenderungen". However, extracts for real estates only covered by plrs of law status "inKraft" should not get slower.

@svamaa
Copy link
Collaborator

svamaa commented Oct 3, 2024

To conclude on the recent testing:

  • in 2 cases (BE & BS) it did not make any difference (I tested with parcels that do have both law status).
  • in 2 cases it slightly does (TI & BL).
  • There are no errors found so far.
    How shall we proceed with this PR? We could merge it if it does not harm anyone but reduces the time slightly. I'd be fine with that.

@lopo977
Copy link
Collaborator

lopo977 commented Oct 3, 2024

If it doesn't complicate code maintenance and BL agrees, it can be merged for us (TI).

@peterschaer
Copy link
Collaborator

It's ok for me to merge.

@voisardf
Copy link
Collaborator

voisardf commented Oct 4, 2024

Same here. In favour for merging - even if the performance does not improve much. 👍

Copy link

codecov bot commented Oct 8, 2024

Codecov Report

Attention: Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 85.74%. Comparing base (86fe195) to head (ef97229).
Report is 24 commits behind head on master.

Files with missing lines Patch % Lines
...oereb/contrib/data_sources/standard/sources/plr.py 83.33% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2050      +/-   ##
==========================================
+ Coverage   85.51%   85.74%   +0.22%     
==========================================
  Files         120      120              
  Lines        5276     5274       -2     
==========================================
+ Hits         4512     4522      +10     
+ Misses        764      752      -12     
Flag Coverage Δ
unittests 85.74% <91.66%> (+0.22%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@michmuel michmuel requested a review from svamaa October 16, 2024 09:51
@svamaa svamaa merged commit b917447 into master Oct 17, 2024
12 checks passed
@svamaa svamaa deleted the change-legend-entries-retrieval branch October 17, 2024 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants