[Bug 858842] New: Font Installation Has a Performance Problem (fc-cache + gnome-settings-daemon)
https://bugzilla.novell.com/show_bug.cgi?id=858842 https://bugzilla.novell.com/show_bug.cgi?id=858842#c0 Summary: Font Installation Has a Performance Problem (fc-cache + gnome-settings-daemon) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: pgajdos@suse.com ReportedBy: sknorr@novell.com QAContact: qa-bugs@suse.de Found By: Documentation Blocker: --- When installing fonts, especially when installing multiple fonts at once, I see very high CPU & RAM usage* (once, when I installed updates for 50 fonts at once, my computer sat unusable for more than an hour and gobbled up all of my 4 GB of RAM). top reports that the two main culprits for this behaviour are fc-cache and gnome-settings-daemon. So, maybe this bug is Gnome-related, too. (Intel Core 2 Duo, ~2.5 GHz laptop, 4 GB RAM.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858842
https://bugzilla.novell.com/show_bug.cgi?id=858842#c1
Stefan Knorr
https://bugzilla.novell.com/show_bug.cgi?id=858842
https://bugzilla.novell.com/show_bug.cgi?id=858842#c2
L. A. Walsh
https://bugzilla.novell.com/show_bug.cgi?id=858842
https://bugzilla.novell.com/show_bug.cgi?id=858842#c3
Petr Gajdos
1) the one you mention where the entire cache is rebuilt with each font installed: pointless. It should should be done, at MOST, once -- if user is
Correct. This is related to dropping suseconfig.* scripts, see bug 773575 for details. fontpackages.changes entry says: ------------------------------------------------------------------- Mon Sep 30 08:44:46 UTC 2013 - pgajdos@suse.com - run fonts-config only once when installing or upgrading more fonts in one transaction ------------------------------------------------------------------- This change unfortunately haven't hit 13.1, but it should be included in next openSUSE release. Please test in beta versions and let me know how it went.
2) 2nd bug doubling the pain is only on 64-bit systems.
Linda, please stop discussing this in three different bugs. Thanks. Stefan, thanks for reporting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858842
https://bugzilla.novell.com/show_bug.cgi?id=858842#c4
--- Comment #4 from L. A. Walsh
1) the one you mention where the entire cache is rebuilt with each font installed: pointless. It should should be done, at MOST, once -- if user is
Correct. This is related to dropping suseconfig.* scripts, see bug 773575 for details.
2) 2nd bug doubling the pain is only on 64-bit systems. Linda, please stop discussing this in three different bugs. Thanks.
Please realize the fix you claim is in for 13.2 doesn't fix issue #2 nor does it address issue/bug #856476. fc-cache will still be run twice -- for 32&64 bit archs (#2) fc-cache runs synchronously in foreground as regular user and again as root, taking ~5 minutes each each time the /usr/share/fonts dir is touched (which is often as my font-libs are 3-way synchronized between machines). (bug856476) Having been dealt with QA for decades and having been in QA -- bug reporters are always advised NOT to combine bugs unless they absolutely know they are the same root cause --- In this case, you have advised me not to file 3 separate bugs because you don't seem to realize that the other two issues won't be solved by rpm post-install scripts being accumulated into suseconfig-post install scripts. On top of that -- suseconfig has had this bug in the past when they were rolled in -- If I installed a new font via rpm, I had to wait through a suse config for tex-caching scripts -- which I never used (and have attempted to make sure are not on my system (unless I am specifically using them)). The bug "fix" you think solves the other 2 issues mentioned, doesn't. And the fix you think fixes it is itself a problem in the same class as bug856476 -- updating all that stuff in foreground while the user is waiting). Please don't presume that a user describing 3 or more different problems with a product should roll all the problems into 1 bug. That's not good QA practice. all be rolled into 1 bug -- it helps things get lost. Example: if someone presumed that a mitigation fix for this bug (moving the cache runs into 1 run) would also, automatically address #2 (bug #853225), and bug #856476 (running fc-cache for regular users and root separate -- and making both wait, synchronously when usually not needed), then those bugs might not get addressed or be marked as "low priority".... ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com