Razvan,
Your email is confusing. To host a Hidden Service you do not need to be a Tor node - we call them relays in the common terminology.
So, a relay relays traffic for Tor clients. This will consume as much as you give. You can throttle the relay bandwidth rate / burst or limit the traffic consumed by accounting per day/week/month, etc. After the speed and traffic limits, next limits are CPU, RAM and so on.
There is no sense in being a relay just to host a hidden service. In fact we do not recommend this, it's better to run the hidden service and relay service in two separate Tor processes if hosted on the same device.
To only host a hidden service you can be a normal Tor client. This will not consume any traffic or relay traffic for other clients, but it will consume as follows: a) all traffic generated by that hidden service. This can be only estimated by you, since it can be 0, it can be 1 MB per week it can be 100 MB per day, etc.
b) consensus data and microdescriptors for relays in the network. I don't have exact numbers for how much is this but count few MBs at every 2 hours just to be sure.
On 5/23/2016 12:56 AM, Razvan Dragomirescu wrote:
Hello everyone,
I'm working on an Internet of Things project and Tor will be a part of it (Hidden Services to be more precise). The nodes however may be battery powered or have slow (or metered) Internet connectivity, so I'm trying to estimate the traffic patterns for a fully functional Tor node. Has this been measured at all? I mean how much traffic should I expect per hour/day/month whatever in order to maintain a good "Tor citizen" node, serving a very low traffic hidden service? I do remember reading something about it needing 4MB per day or something like that, but I can't seem to find that link or page anywhere now... :(.
Any hints on where to find this type of info (or maybe how to measure it myself) would be appreciated.
Thank you, Razvan
-- Razvan Dragomirescu Chief Technology Officer Cayenne Graphics SRL