Re: Minor Copr release 2020-06-19

2020-06-20 Thread Iñaki Ucar
On Sat, 20 Jun 2020 at 00:29, Pavel Raiskup  wrote:
>
> Hey all,
>
> a new versions of copr packages were deployed now to production.  There are
> several small bugfixes (most of them were already hot-fix patched in 
> production
> before), but there are also two major things worth mentioning:
>
> 1. The build task scheduler (priority counting) was fixed once more, now
>for real, I believe.  When you submit a background job, it _will_ be
>processed later than your normal builds (or at the same time, if there's
>capacity, there are no synchronization mechanisms, yet).  Also source 
> builds
>have precedence over binary RPM builds again (see issues #1414 and #1415
>for more info).
>
> 2. Newly, we don't always run createrepo_c after each build (or delete 
> request).
>Iff there are a concurrent createrepo_c requests on the same directory
>(multiple builds finished at a similar time in the same project chroot) we 
> will
>likely group them into a batch and execute the createrepo_c only once for 
> the
>whole batch.  This saves some resources in general, but the major speedup
>will be in large projects (where createrepo_c used to block us 
> historically).

Screenshot of the batch I sent yesterday. Thanks to 1), the number of
pending tasks steadily grows very fast, and thanks to 2) builds are
processed much faster than before. Great work!

-- 
Iñaki Úcar
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org


Re: Minor Copr release 2020-06-19

2020-06-20 Thread Miro Hrončok

On 20. 06. 20 0:29, Pavel Raiskup wrote:

2. Newly, we don't always run createrepo_c after each build (or delete request).
Iff there are a concurrent createrepo_c requests on the same directory
(multiple builds finished at a similar time in the same project chroot) we 
will
likely group them into a batch and execute the createrepo_c only once for 
the
whole batch.  This saves some resources in general, but the major speedup
will be in large projects (where createrepo_c used to block us 
historically).


Thank you so much for this.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org