~5-7 seconds on a quad core Phenom machine.
~3 seconds on a dual Xeon workstation.
During the 4.6 beta phase I re-enabled it (including strigi) on both machines after having it disabled since, err, it was released.Also, has nepomuk stopped being an atrocious resource hog yet? I appreciate the idea, but last time I tried it (which I think was KDE 4.4.3), it was eating a stupid amount of CPU/RAM/disk.
After a short burst of activity (presumably, initial indexing), I no longer see it.
FYI, both machines run Fedora 14/x86_64 and KDE 4.6 RPMS from kde-redhat/unstable.
- Gilboa



Reply With Quote
