On Fri, Nov 10, 2017 at 06:33:09AM -0800, John Reiser wrote: > On 11/10/2017 1058Z, Richard W.M. Jones wrote: > > >24 hours and counting ... > > > >I talked to someone on #fedora-admin about this and it is caused by > >Koji having to load the metadata (files, dependencies etc) of every > >RPM into its database. Combined with the fact this happens to be > >running on s390x and it's texlive, makes it slow. > > Can you be more specific? Is it slow because: > 1. the s390x has a slow or inappropriate CPU for the task? > 2. the VM on the s390x has not enough real RAM, and is page thrashing on a > spinning harddrive? > 3. the database uses a quadratic algorithm that hurts in this case? > 4. the database has very high CPU overhead in general? > 5. "every RPM" means all 30,000 .rpm in Fedora, not just the 300 for > texlive? > (And if so, then why isn't tagging slow for _every_ package?) > 6. some other specific reason(s)? > > Indexing 1GB of data should take no more than a few minutes.
I don't have any access to the machine so I'm not in a position to say. I will note however that the previous successful build of texlive took 4 hours in total (that's building, adding to the database and tagging). This one has been running for 30 hours and still has not completed. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
