GenericProjectManager improvements

Andreas Pakulat apaku at gmx.de
Sun Oct 5 10:18:30 UTC 2008


On 05.10.08 11:31:59, Niko Sams wrote:
> > No, one KDirWatch instance can watch up to 8192 files+directories if you
> > use inotify and if the inotify limit hasn't been changed. If however the
> > distribution, or user decided to use another watch-method, like fam/gamin
> > or even polling the filesyste, then you can watch as many files+directories
> > with 1 KDirWatch instance as you want (no idea wether fam/gamin have a
> > maximum limit here)
> Ah - ok - I see.
> So this is only a problem if a project has more than 8000 directories.
> And wouldn't
> it be easier in that case that KDirWatch would handle the multiple
> inotify instances
> transparently?

Probably, but that class has the problem of many others in kdelibs: No real
maintainer, just people touching it every once in a while... 
 
> The problem that we still have (with multiple inotify instances if the
> limit is exceded)
> is performance - especially if polling is used I guess.
> Do we have to find a solution for that now?

No, if a user doesn't have inotify or fam/gamin available on linux, then
he's basically doomed anyway. KDirWatch is used in tons of places, for
example strigi watches every file it indexes...

We don't need to worry about the performance of things we use, just about
the performance of our own code in this specific case.

Andreas

-- 
Be security conscious -- National defense is at stake.




More information about the KDevelop-devel mailing list