On streda 11 August 2010 11:08:53 Katarina Machalkova wrote:
OK, so obviously the more YCP files it has to parse, the longer it takes to launch. Comparing y2-users (lots of YCP files) with y2-inst_release_notes (relatively few YCP files), the former takes ~5 minutes to launch, while the latter needs only 5 seconds.
Soo - this can't be a secret YaST feature, can it? :) Am I doing anything wrong? Did upgrade mess something up? If so, what? Has anyone seen something like this before (in bugzilla etc.)? If needed, I can make my laptop available if someone wants to play with it Greetings
Please file me a bug, with y2logs, without strace, and I'll fix the unbuffered reads to make stracing more useful.
For the record: I've installed yast2-core 2.19.3 with buffered read patch from YaST:Head repository. It seems that buffering the reading of #includes did the trick.Using y2-users as a benchmark again, the patch reduces start-up time from 4.5 minutes to 12 seconds.
Now someone can come up with a conspiration theory, why it might have been *that* bad with unbuffered reads (it felt like pkg management in 10.1 again)
Related ticket: http://bugzilla.novell.com/show_bug.cgi?id=629882 Thanks to Martin for prompt fixing
Shouldn't it go out as maintenance update for 11.3? Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org