[kde-freebsd] QFilesSystemWatcher instead of polling/FAM

[Tijl Coosemans]

On Monday 23 August 2010 23:51:31 Alberto Villa wrote:
> On Monday 09 August 2010 11:01:56 Tijl Coosemans wrote:
>> I've attached what I believe to be the final version of the kdelibs
>> patch. It uses polling by default for NFS mounts now and fixes a few
>> other things. Unless someone finds a problem with it, I'll submit that
>> as well.
> 
> hey tijl, thanks for working on this!
> 
> but... i've applied the patches (attached... the kde one was rewritten 
> for kde 4.5 by dima) to my system and the performance is terrible
> 
> some (maybe useless) details:
> CPU: Intel(R) Core(TM) Duo CPU      T2300  @ 1.66GHz
> real memory  = 1610612736 (1536 MB)
> FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #4 r211492: 
> Thu Aug 19 23:52:10 CEST 2010     
> root at echo.hoth:/usr/obj/usr/src/sys/TPR60  i386
> qt-4.7.0.b2
> kde-4.5.0
> just for reference... i don't have any NFS mount
> i don't think anything's missing...
> 
> what happens:
> lots of processes go into kqread and ucond (which, i've understood, is 
> related to i/o) statuses, and long time passes before they're still 
> usable, just like (snapshot taken right now)...
> - ucond   1   2:38  1.46% kdeinit4: kdeinit4: konqueror --silent 
> (kdeinit4)
> - kqread  1   1:45  0.10% /usr/local/kde4/bin/kontact
> - ucond   0   1:33  0.00% /usr/local/kde4/bin/amarok
> - ucond   0   0:39  0.00% /usr/local/bin/virtuoso-t +foreground 
> +configfile /tmp/vir
> - kqread  0   0:23  0.00% kdeinit4: kdeinit4: kmix (kdeinit4)
> - ucond   0   0:17  0.00% /usr/local/kde4/bin/nepomukservicestub 
> nepomukstrigiservic
> - kqread  0   0:14  0.00% kwin (this one makes the whole system 
> completely unusable)
> - kqread  1   0:03  0.00% kdeinit4: kdeinit4: krunner --nocrashhandler 
> (kdeinit4)
> - ucond   1   0:02  0.00% /usr/local/kde4/bin/knotify4
> - kqread  0   0:02  0.00% /usr/local/kde4/bin/konversation -caption 
> Konversation -ic
> - kqread  0   0:01  0.00% kdeinit4: kdeinit4: kwalletd (kdeinit4)
> - kqread  0   0:01  0.00% /usr/local/kde4/bin/nepomukservicestub 
> nepomukontologyload
> 
> i know less than zero on this matter, so, please, let me know how can i 
> be more useful :)

Does this happen as soon as you login, or only after a while?
Can you give me the output of "sysctl kern.openfiles"?

The kqread status should be ok. It's the status of the QFileSystemWatcher
worker thread when it's waiting for new events. The status of other
threads would be more useful, so can you give me the output of
"top -Ha all > file" when it happens again?

I'm not sure what ucond means. Usually a kde process has 2 threads, one
in the select state (application thread) and one in kqread state (qfsw
thread), but sometimes I see a 3rd in ucond state. This hasn't caused
any problems for me yet, but I'll try to take a closer look at that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-freebsd/attachments/20100825/e27b3d13/attachment.sig