Running giFT without issuing queries

When running giFT, and hence OpenFT, without issuing any queries the following traffic was measured during three separate sessions.

• Session 1 consumed 878 bytes per second of which 81% was TCP traffic.
• Session 2 consumed 880 bytes per second of which 90% was TCP traffic.
• Session 3 consumed 1742 bytes per second of which 93% was TCP traffic. The increased traffic appears to have been caused by new transmissions of share information to parent nodes, since TCP data dramatically increased for this session. Examining the captured data closer confirms the theory of share indexing.

It is hard to provide a good approximation on the traffic amount. If the giFT daemon is running for longer periods of time the first two sessions are more appropriate. If the daemon is started only when the user wants to run a client, such as giFTcurs, additional traffic depending on how many files the user is sharing will be caused. For the further discussions an average value of 900 bytes per second will be assumed, unless explicitly specified otherwise. This leads to 650 bytes per second caused purely by OpenFT, without any queries being issued.