Comment 6 for bug 998759

I see two problems:

1) indicator-multiload is causing (via dbus?) hud-service to do "something" (update/reload cache?) each time indicators get refreshed. indicator-multiload does not do any "strange" network activity by itself, strace shows quite sane behavior (access to /proc and /sys and such).

2) each hud-service "update" initiated by indicator-multiload is casuing some 0.5MB network exchange (if home directory is on NFS), about half with nfs port and half with nfs lockd. I tcpdumped both sessions. Lock protocol is all binary, looks like repeating lock requests. On nfs port, it does the same over and over again. I counted this snippet called 88 times during one hud-servide "update":

q.........O.W.7|N.O... ..yO... ..y............SQLite format 3......@ .........................................................................-.!
.....I....I.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................W.../..windexapplication_indexusage.CREATE INDEX application_index on usage (application)\........tableusageusage.CREATE TABLE usage (application text, entry text, timestamp datetime)

As a workaround, I can:
1) reduce frequency of indicator refresh
2) kill hud-service (and so this network activity stops)