Michael Calmer wrote: % Hi, % attached you can find a little present for the new year :-) % % We did some profiling on reposync and found out that the PL/SQL function % refresh_newest_package is one big bottleneck. Especially with postgres it % takes most of the time of a reposync. % % The reason is, that it always calculate the newest version of all package % names in a channel. It should be sufficient to only calculate the newest % package of the package name reposync is currently working on. % % The patch add a new procedure with an additional paramater "package_name_id" % which only work on this name_id. % % Some numbers: % - repo with ~2500 RPMs % % postgres: old: 2:30 hours new: ~30 minutes % oracle: old: 2:45 hours new: ~36 minues % % I hope I did all the DB upgrade scripts right. Please double-check them. % Thanks.
Hi Michael, I reviewed your patch. I did some minor changes in formating and one rather bigger - duplicated code in two similar procedures refresh_newest_package() and refresh_newest_package_light() so I merged them into original procedure. Anyway the code is commited. Thanks for the patch. Regards, -- Michael Mráka Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
