Just a proof of concept for: Large implementations need a viable upgrade path to 1.9.x - TRUNK-4117 #462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://tickets.openmrs.org/browse/TRUNK-4117
This is not a fix. It is just trying to see if applying the change sets to empty obs and encounter tables, and then copying the data into them, can improve the performance. I have tested this on Mathew's (Masaka site in Uganda) 6.72 GB database and it took 35 minutes to complete the upgrade from version 1.8.4 to version 1.11
He told me that it took him more than a week to do an upgrade which did not complete and then he aborted it.
This database has:
patients = 21,604
encounters = 441,944
observations = 10,576,185