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

[PERFORMANCE] Merging of duplicates takes too long and sometimes leads to a Server Connection Lost #8615

Closed
Tracked by #7734
markusmann-vg opened this issue Mar 29, 2022 · 4 comments
Labels
change A change of an existing feature (ticket type) needs-response Response from the issue creator required performance Issues that are meant to increase the performance of the application

Comments

@markusmann-vg
Copy link

markusmann-vg commented Mar 29, 2022

Feature Description

One of the use cases that health departments encounter often is the merging of duplicates. For this use case the performance is essential to be productive.

Problem Description

Even limiting the search in terms of time does not lead to any improvement.
After the health department has to merge several hundred duplicates, they need better performance of the system here.
The duration of merging duplicates takes in some cases 10 to 15 minutes and often even leads to a Server Connection Lost.

The Logs can be found here

Proposed Change

Possible Alternatives

Additional Information

@markusmann-vg markusmann-vg added the change A change of an existing feature (ticket type) label Mar 29, 2022
@MartinWahnschaffe MartinWahnschaffe added important performance Issues that are meant to increase the performance of the application labels Mar 29, 2022
@StefanKock
Copy link
Contributor

Unclear: Is the merge view not loading does the save action not finish in reasonable time?

@StefanKock StefanKock added the needs-response Response from the issue creator required label Apr 6, 2022
@MartinWahnschaffe
Copy link
Contributor

Could be related to #8697 and will be analysed there.

@StefanKock
Copy link
Contributor

Could be related to #8697 and will be analysed there.

Update: Will probably be improved by #9054.

@MartinWahnschaffe
Copy link
Contributor

Also improved by #11465 and #11469

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change A change of an existing feature (ticket type) needs-response Response from the issue creator required performance Issues that are meant to increase the performance of the application
Projects
None yet
Development

No branches or pull requests

3 participants