[tahoe-dev] running a helper - bandwidth considerations

Jody Harris imhavoc at gmail.com
Mon Feb 15 15:56:32 UTC 2010

If I'm understand it, trickle might allow me to limit the bandwidth
consumption for a helper, but it doesn't offer bandwidth consumption

I think that restricting bandwidth is less useful than keeping track of

Running the helper on my relatively old, relatively slow server did (for a
single client) not seem to cause performance problems for the server.
(Although, I would probably need to switch to a newer, faster server to
support more than two concurrent connections.) My main concern is being able
to 'bill' for bandwidth.

- Think carefully.
- Contra mundum - "Against the world" (St. Athanasius)
- Credo ut intelligam - "I believe that I may know" (St. Augustin of Hippo)

On Mon, Feb 15, 2010 at 8:21 AM, Sam Mason <sam at samason.me.uk> wrote:

> On Fri, Feb 12, 2010 at 07:26:43AM -0700, Jody Harris wrote:
> > Is there any way to monitor the bandwidth-usage per node when running a
> > helper.
> >
> > I would like to offer a helper to my node users, but I will have to have
> > some way of allocating costs on a per-node basis.
> >
> > I am not seeing any log messages from the helper.
> >
> > Any thoughts are appreciated.
> I've not tried it, but would something like trickle[1] be helpful?  It's
> more for keeping control of bandwidth, but it provides an option to dump
> out information regularly which may help you.
> --
>  Sam  http://samason.me.uk/
>  [1] http://monkey.org/~marius/trickle/
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100215/402814bf/attachment.html>

More information about the tahoe-dev mailing list