Hmm, okay, I ran a little analysis on your histograms...

cat firefox.ecryptfs.slow.strace | sed "s/(.*//" | sort -u > words
for i in $(cat words); do echo -n "$i "; grep -c "^$i" 
firefox.ecryptfs.fast.strace; done | sort -k 2 -n > /tmp/histogram_fast
for i in $(cat words); do echo -n "$i "; grep -c "^$i" 
firefox.ecryptfs.slow.strace; done | sort -k 2 -n > /tmp/histogram_slow
tail -n 10 /tmp/histogram_*

==> /tmp/histogram_fast <==
lseek 1057
close 1089
futex 1260
open 1502
madvise 2249
stat 2661
writev 2937
write 3851
poll 8600
read 11722

==> /tmp/histogram_slow <==
lseek 1087
close 1102
open 1529
stat 2841
madvise 3828
futex 13392
writev 15315
write 20113
poll 49424
read 64545

Looks like your slow version is doing a *lot* more futex, writev, write,
poll, and read.

Specifically, there's a lot of:
read(3, 0x7f93049ae074, 4096)           = -1 EAGAIN (Resource temporarily 
unavailable)

grep "Resource temporarily unavailable" firefox.ecryptfs.fast.strace  | wc
   6407   57691  557685
grep "Resource temporarily unavailable" firefox.ecryptfs.slow.strace | wc
  46904  422249 4081862

I don't really know what's at that address, and I don't yet see what
eCryptfs might be doing wrong here.  Considering that firefox is working
well with your other users on eCryptfs, this is strange.

On the user with the "slow" firefox, could you mv ~/.mozilla
~/.mozilla.orig.  The next time you open Firefox, it will recreate the
.mozilla directory (losing your bookmarks, cookies, passwords, etc).
You can restore it again by moving it back into place.  But see if your
firefox is any faster with a brand new .mozilla config.

:-Dustin

:-Dustin

:-Dustin

** Changed in: ecryptfs-utils (Ubuntu)
       Status: New => Incomplete

** Changed in: ecryptfs-utils (Ubuntu)
   Importance: Undecided => Low

** Changed in: firefox-3.5 (Ubuntu)
       Status: New => Incomplete

** Changed in: firefox-3.5 (Ubuntu)
   Importance: Undecided => Low

-- 
ubuntu karmic firefox 3.5.4 slow on ecryptfs
https://bugs.launchpad.net/bugs/470016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to