Re: Beagle on encrypted partitions yeilds horrible system performance
David Nielsen wrote: As Fedora now proposes encryption by default as of F9 during install, this would be a spanner in the works for enabling beagle provided the impact can't be lessened. Afaik its only enabled by default in the prerelease versions for testing and should be opt in for the release. ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Beagle on encrypted partitions yeilds horrible system performance
I am hitting kind of a nasty performance problem, my current test setup is a two disk mdraid RAID0 setup with lvm ontop of a dmcrypt, all partitions beagle touches are ext4. Now every time beagle 0.3.4 indexes a folder, the entire system becomes near non responsive, typing yeilds detection of multiple key presses and kcryptd and beagle-helper are combined using 100% CPU (in about a 80/20 split with beagle being the 20%). I understand that there is to be a certain degree of overhead but this seems excessive. So in the interest of serving my users I was wondering if there was anything to do to lessen the impact, I am planning to propose Beagle be turned on again by default in F10 (I was sadly to late to propose the feature for F9 but I can get all the prep work done for F10 with certainty). As Fedora now proposes encryption by default as of F9 during install, this would be a spanner in the works for enabling beagle provided the impact can't be lessened. - David ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle on encrypted partitions yeilds horrible system performance
I am hitting kind of a nasty performance problem, my current test setup is a two disk mdraid RAID0 setup with lvm ontop of a dmcrypt, all partitions beagle touches are ext4. Now every time beagle 0.3.4 indexes a folder, the entire system becomes near non responsive, typing yeilds detection of multiple key presses and kcryptd and beagle-helper are combined using 100% CPU (in about a 80/20 split with beagle being the 20%). Hmm... and the encrypted partition is not a red-herring ? I mean, could it be ext4 ? Could it be extended attribute in ext4 ? Could it be just some undetected bug in beagle ? Ahh ... ok - kcryptd and beagle-helper are combined using 100% CPU (in about a 80/20 split with beagle being the 20%) - so there is something to do with kcryptd. Can you try this test ? Take a reasonably large text file. Run beagle-extract-content on it on a normal partition and your dmcrypted ext4 partition. If the time taken differs significantly, then there is a sure problem there and we can start from there. Unfortunately I am too far from using a dmcrypt partition on ext4 so it will be hard for me to test this directly :-( - dBera -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE / Mandriva / Inspiron-1100 ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle on encrypted partitions yeilds horrible system performance
Hi, On Wed, Mar 26, 2008 at 11:12 AM, Debajyoti Bera [EMAIL PROTECTED] wrote: I am hitting kind of a nasty performance problem, my current test setup is a two disk mdraid RAID0 setup with lvm ontop of a dmcrypt, all partitions beagle touches are ext4. Now every time beagle 0.3.4 indexes a folder, the entire system becomes near non responsive, typing yeilds detection of multiple key presses and kcryptd and beagle-helper are combined using 100% CPU (in about a 80/20 split with beagle being the 20%). Hmm... and the encrypted partition is not a red-herring ? I mean, could it be ext4 ? Could it be extended attribute in ext4 ? Could it be just some undetected bug in beagle ? Ahh ... ok - kcryptd and beagle-helper are combined using 100% CPU (in about a 80/20 split with beagle being the 20%) - so there is something to do with kcryptd. Beagle does do a tremendous amount of IO, so I don't think it's unreasonable that reading a large chunk of data off the disk and writing large chunks to the index is CPU-bound when we're talking about an encrypted home directory. I would be interested in knowing if other similarly IO-heavy operations (like find /) are also CPU bound. Does setting BEAGLE_STORAGE_DIR to something on a different (non-encrypted) home directory change things? There may be no real solution to this, short of having Beagle's scheduler throttle itself more extremely, which will slow down indexing. Load average is already taken into account, but maybe it should be given more weight. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle on encrypted partitions yeilds horrible system performance
On Wed, 2008-03-26 at 11:54 -0400, Joe Shaw wrote:
I would be interested in knowing if other similarly IO-heavy
operations (like find /) are also CPU bound.
Probably a more accurate representation would be:
find dir -type f -exec cat {} /dev/null \;
So that the content of files is read, really invoking the crypt
overhead.
b.
signature.asc
Description: This is a digitally signed message part
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
