Comment # 168 on bug 1112824 from Robert Munteanu

(In reply to Timo Jyrinki from comment #167)
> Something on my mind is to check that 20181015 <-> 20181018 snapshot delta
> mentioned in comment #160 and see if the difference is as big as what I have
> there on the video between distributions.

I think this is the first step that can be done. I unfortunately don't have a
spare machine and the time to run the tests, but I think a binary search in the
updates that were applied between 20181015 and 20181018 would help pinpoint the
root cause.

Assuming that the 20181018 snapshot has broken performance, there are N package
updates between 20181015 and 20181018. One can split these N package updates in
N1 and N2. It should happen that one of these contains the problematic update,
so applying N1 (for instance) should reproduce the problem but not N2. And so
on and so forth.

If anyone has the possibility to do this I think it would be a worthwhile
exercise.