DNOTIFY support and some timing

Christian Esken c.esken at cityweb.de
Sun Feb 23 14:07:18 GMT 2003


is there a good reason not to compile in DNOTIFY support by default?
The code in kio/kio/kdirwatch.cpp already checks the kernel version.
I agree, that there should be a possibility do --disable-dnotify ,
but default should be enabled.

For example SuSE8.1 (ships Kernel 2.4.19 and KDE3.0) has
not compiled KDE with "--enable-dnotify".
AFAIK KDE3.0 already had dnotify support?!?

Remark: I came across this, while working on a list of tips on how to
use KDE3 on slow computers. On "low end" computers like mine
(PIII - 450Mhz, 128MB Ram) doing polling has MAJOR impact on
overall KDE performance. Application startup and overall resposiveness
is much better with DNOTIFY. I blame this on the continuous task switching
from and to kded.

Examples (both time everything was compiled including --enable-debug=full switch):

Application  With / without DNOTIFY support (Time used for launching App.)
kwrite       4-6s / 6-10s
kedit        2-3s / 3-5s


More information about the kde-core-devel mailing list