[Pulp-list] Long upgrade times from 2.6 -> 2.8

[Eric Helms]

Howdy,

We (Katello) have had users reporting incredibly long upgrade times when
upgrading from 2.6 to 2.8. This occurs during the pulp-manage-db step that
is run as the beginning of our installers upgrade process. Based on the
numbers below, does this make sense at all?

Some numbers:

18 hour upgrade
1.5 TB /var/lib/pulp
100GB MongoDB


Thanks,
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160701/7e4d2046/attachment.htm>