Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3055 - faked hogs CPU

Attached to Project: Arch Linux
Opened by Leslie Polzer (skypher) - Monday, 08 August 2005, 10:31 GMT
Last edited by James Rayner (iphitus) - Sunday, 15 October 2006, 10:51 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I don't know whether this is related to

http://bugs.archlinux.org/index.php?do=details&id=1151

but since some weeks makepkg is terribly slow (and slows down the whole system if I do not nice it) - mostly in the beginning. top shows 'faked' at about 80% CPU time and each configure step takes ages. I think compilation itself is not affected very much, though.

FYI:
% pacman -Q | wc -l
768

Leslie
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Wednesday, 03 January 2007, 20:01 GMT
Reason for closing:  None
Comment by Igor Galić (jMCg) - Wednesday, 10 August 2005, 21:57 GMT
I've got a similar problem with makepg when running it several times in a row, it uses up all IPC queues, only solution i found so far is reboot (which sucks.)

I already posted that bug of mine, but i don't know where it vanished to..
Comment by Leslie Polzer (skypher) - Tuesday, 20 September 2005, 18:49 GMT
Running pacman-optimize seems to remedy all pacman and makepkg speed issues. I suggest mentioning this binary somewhere as I just stumbled by accident over it (and I'd consider myself a very inquisitive user ;) ).
Comment by Alexander Baldeck (kth5) - Friday, 21 April 2006, 11:53 GMT
i built man-pages, once as a user and once as root on a Celeron D 2.4ghz, 768MB DDR400 and a 7200rpm SATA2 disk with 8mb cache. these are my timings:

$ cd man-pages
$ time makepkg -c
...
real 2m56.275s
user 0m35.686s
sys 1m39.282s

<reboot to avoid caching>

$ su
$ time makepkg -c
...
real 1m3.957s
user 0m14.161s
sys 0m47.607s

so i assume it's fakeroot that hogs ressources when makepkg is run as a user. it is extremely noticable the more files there are to `find` in src/ and pkg/.
Comment by arjan timmerman (blaasvis) - Thursday, 22 June 2006, 12:46 GMT
could you try building fakeroot 1.5.8 and see if it helps ?
Comment by Roman Kyrylych (Romashka) - Saturday, 25 November 2006, 14:39 GMT
Is this still valid?

Loading...