Mailinglist Archive: opensuse (3566 mails)
| < Previous | Next > |
Re: [opensuse] beagle again - was: Disk I/o In 10.2 Significantly Slower Than 1.0(reiser)
- From: "Joe Shaw" <joe@xxxxxxxxxxx>
- Date: Fri, 20 Apr 2007 11:53:11 -0400
- Message-id: <f8203010704200853o67de3d8fl410a005f67eae78e@xxxxxxxxxxxxxx>
Hi,
On 4/20/07, Morten Bjørnsvik <morten.bjornsvik@xxxxxxxxxxxxxxxxxx> wrote:
It definitely should not be nice -19. You probably mean nice +19?
The version that ships with openSUSE 10.2 doesn't nice itself at all,
so any adjustments are done either by the user or the kernel.
I feel like a broken record, but the updated version in the build service here:
http://software.opensuse.org/download/Beagle/
does mitigate this in a few ways. First, the beagled-helper process
(the one that does the actual indexing) is nice +17 and tells the
kernel's scheduler that it is a batch process, so the kernel never
adjusts it from +17. (Otherwise the scheduler in 10.2 could lower it
to +12, and a stepping scheduler might eventually set it to -19.) The
main daemon process isn't niced, but that'll change in the next
release to a modest +7, IIRC. The main daemon process usually isn't
too heavy on CPU usage.
Well, they're not... no Mono process has a higher priority as far as I
know. I suspect you're cherry picking certain mono apps that appear
to have high CPU usage -- ZMD and Beagle, in particular. ZMD itself
isn't even particularly CPU-hungry, the external zypp components (in
C++) are a much bigger consumer than ZMD itself. There are plenty of
Mono apps, like F-Spot and Tomboy, which have no impact on CPU at all.
Beagle's is higher mainly because it actively does more work than any
of the other three. There are bugs which can make it's CPU usage
excessive too, but we think we've pretty much squashed all of them in
the latest version.
Is the system slow because of CPU usage, or because of disk usage? If
you don't have DMA enabled for your disk, this could slow the system
down quite a bit.
You could run some tests for this; running the iozone test might be
good, doing dd might help, and lastly doing something like "find /"
would walk the tree, mess with the cache, etc. You could see if those
also have a big effect on system interactivity.
Joe
N‹§²æìr¸›y隊Z)z{.±ï®žË›±Êâmê)z{.±ê+€Z+i×b¶*'jW(šf§vǦj)h¥éìºÇ¾…éi¢—§²ë ¢¸
On 4/20/07, Morten Bjørnsvik <morten.bjornsvik@xxxxxxxxxxxxxxxxxx> wrote:
The priority of beagle-indexing must be completely wrong it should be nice -19
It definitely should not be nice -19. You probably mean nice +19?
The version that ships with openSUSE 10.2 doesn't nice itself at all,
so any adjustments are done either by the user or the kernel.
I feel like a broken record, but the updated version in the build service here:
http://software.opensuse.org/download/Beagle/
does mitigate this in a few ways. First, the beagled-helper process
(the one that does the actual indexing) is nice +17 and tells the
kernel's scheduler that it is a batch process, so the kernel never
adjusts it from +17. (Otherwise the scheduler in 10.2 could lower it
to +12, and a stepping scheduler might eventually set it to -19.) The
main daemon process isn't niced, but that'll change in the next
release to a modest +7, IIRC. The main daemon process usually isn't
too heavy on CPU usage.
It has been discussed before, but why is mono apps running with high priority?
Well, they're not... no Mono process has a higher priority as far as I
know. I suspect you're cherry picking certain mono apps that appear
to have high CPU usage -- ZMD and Beagle, in particular. ZMD itself
isn't even particularly CPU-hungry, the external zypp components (in
C++) are a much bigger consumer than ZMD itself. There are plenty of
Mono apps, like F-Spot and Tomboy, which have no impact on CPU at all.
Beagle's is higher mainly because it actively does more work than any
of the other three. There are bugs which can make it's CPU usage
excessive too, but we think we've pretty much squashed all of them in
the latest version.
Everything else hangs while beagle-indexing is being done.
Is the system slow because of CPU usage, or because of disk usage? If
you don't have DMA enabled for your disk, this could slow the system
down quite a bit.
You could run some tests for this; running the iozone test might be
good, doing dd might help, and lastly doing something like "find /"
would walk the tree, mess with the cache, etc. You could see if those
also have a big effect on system interactivity.
Joe
N‹§²æìr¸›y隊Z)z{.±ï®žË›±Êâmê)z{.±ê+€Z+i×b¶*'jW(šf§vǦj)h¥éìºÇ¾…éi¢—§²ë ¢¸
| < Previous | Next > |