* Marius Schwarz:
> I have just create(d/ not finished yet, started 15 minutes ago) a ~2.5
> GB rpm and found, that rpmbuild is an extrem bottleneck.
>
> IMHO, this is caused by a fileread function which reads files in 32k
> blocks, which is very slow and extrem IO intensive. The result is a
> task running at 1 core at 100% perma. With changes to larger chunks,
> we can speed up so many build tasks on the farm.
That's unlikely. 32K is not a small buffer size.
It's more likely that time is spent during compression.
> [pid 2604060] read(5, "B s_I ts_I u:_I g_I R_I E_I n_I "..., 32768) = 32768
> [pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222,
> tv_nsec=480654716}) = 0
> [pid 2604060] clock_gettime(CLOCK_REALTIME, {tv_sec=1657579222,
> tv_nsec=480763606}) = 0
>
> and I don't think, this tasks needs to read the clock that often too.
strace shouldn't see a system call here because clock_gettime should be
handled in the vDSO. This suggests something is wrong with the system
(unless it's some obscure variant that really doesn't have vDSO support).
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
