https://bugs.kde.org/show_bug.cgi?id=331848
--- Comment #7 from Martin Steigerwald <m...@teamix.de> --- FWIW Nepomuk/Virtuoso is still running on NFS, as I never found any serious issues with that. It works nicely meanwhile. But it may contribute to performance issues and Nepomuk against local storage might be faster. Machine is connected with 1GBit ethernet and I consider latency to be quite low: ms@mango:~> ping netappfasnfsmachine PING netappfasnfsmachine (172.21.254.12) 56(84) bytes of data. 64 bytes from netappfasnfsmachine (172.21.254.12): icmp_seq=1 ttl=255 time=0.115 ms 64 bytes from netappfasnfsmachine (172.21.254.12): icmp_seq=2 ttl=255 time=0.179 ms 64 bytes from netappfasnfsmachine (172.21.254.12): icmp_seq=3 ttl=255 time=0.179 ms 64 bytes from netappfasnfsmachine (172.21.254.12): icmp_seq=4 ttl=255 time=0.201 ms 64 bytes from netappfasnfsmachine (172.21.254.12): icmp_seq=5 ttl=255 time=0.200 ms ^C --- netappfasnfsmachine ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.115/0.174/0.201/0.035 ms Anyway, waiting for KDE SC 4.13 packages to see how it performs with Baloo. I hope Baloo can run on NFS. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
