So far, it's lingering around 12 hours and 1-2 db cpus.
Refine, and make this information well known.
awight | |
Oct 16 2015, 5:54 PM |
F2766984: civi-4.6-upgrade-20151024.log | |
Oct 25 2015, 8:57 AM |
So far, it's lingering around 12 hours and 1-2 db cpus.
Refine, and make this information well known.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T90630 Recurring Payments Reporting | |||
Resolved | • mepps | T97372 Enable ability to look up contacts by phone number | |||
Resolved | None | T77910 [epic] Upgrade Civi to 4.6 & integrate new reporting | |||
Resolved | awight | T99844 Install Civi 4.6 to production | |||
Resolved | Eileenmcnaughton | T99842 [epic] Install 4.6 to staging and test like hell | |||
Resolved | awight | T115736 Time the upgrade itself, and note the load it puts on the database |
We need the per-step timing, but I can't tell whether the patch is already merged to civi-4.6.9, and I'm too lazy to reinstall a 4.2 schema. @Eileenmcnaughton would you mind linking here to the newer patch?
See upstream patch https://github.com/civicrm/civicrm-core/commit/0db15f7fb0120e60510bf42322799ad05666e0ec and local patch https://gerrit.wikimedia.org/r/#/c/242821/
@Eileenmcnaughton
Please take a peek at the log above, and let us know if any of the slow steps can be skipped. Nothing jumped out at me...