On 2016-09-20 20:58, Roger Dingledine wrote:
On Tue, Sep 20, 2016 at 07:20:03PM +0200, shraptor wrote:
What's up with these messages I get in tor-arm and log?
Caching new entry debian-tor for debian-tor [62 duplicates hidden]
What is tor doing??
Sep 20 19:10:21.000 [notice] Caching new entry
Hi all,
I'm looking at some traffic patterns for my Exit relay, and I'm frankly
a bit disappointed with the utilization.
Currently it's running at a load average of 0.3-0.5, and CPU idle at
70-80%.
We're not limited on Bandwidth (tests show that our max cap is more than
safe to produce), yet,
In short, yes.
On Sep 21, 2016 5:02 AM, "D.S. Ljungmark" wrote:
> Hi all,
>
> I'm looking at some traffic patterns for my Exit relay, and I'm frankly
> a bit disappointed with the utilization.
>
> Currently it's running at a load average of 0.3-0.5, and CPU idle at
> 70-80%.
>
>
> We're not li
Well, according to this question I asked on Tor's StackExchange, version
0.2.4.26 is still technically in the recommended consensus.
At any rate, running an older version is better for diversity, isn't it?
On Sep 21, 2016 2:13 AM, "shraptor" wrote:
> On 2016-09-20 20:58, Roger Dingledine wrote:
Whoops, forgot to paste the link:
https://tor.stackexchange.com/questions/12638/how-old-is-too-old-tor-versions
On Sep 21, 2016 7:46 AM, "Tristan" wrote:
> Well, according to this question I asked on Tor's StackExchange, version
> 0.2.4.26 is still technically in the recommended consensus.
>
> A
> On 21 Sep 2016, at 20:01, D.S. Ljungmark wrote:
>
> Hi all,
>
> I'm looking at some traffic patterns for my Exit relay, and I'm frankly
> a bit disappointed with the utilization.
>
> Currently it's running at a load average of 0.3-0.5, and CPU idle at
> 70-80%.
>
>
> We're not limited on
> On 21 Sep 2016, at 22:46, Tristan wrote:
>
> Well, according to this question I asked on Tor's StackExchange, version
> 0.2.4.26 is still technically in the recommended consensus.
And it will be the next to go, likely when the next directory authority's
details change, or a serious security
On 21/09/16 15:24, teor wrote:
>
>> On 21 Sep 2016, at 20:01, D.S. Ljungmark wrote:
>>
>> Hi all,
>>
>> I'm looking at some traffic patterns for my Exit relay, and I'm frankly
>> a bit disappointed with the utilization.
>>
>> Currently it's running at a load average of 0.3-0.5, and CPU idle at
> 17 MBytes/s in each direction.
From Atlas graph, your node is currently growing up, so wait few weeks more to
have the real bandwidth consumption, but don’t expect huge change.
17M*B*ps is 140M*b*ps and you already have a good relay :)
This is around the speed expected for standard CPU (150 to
Well, until someone decides to update Orbot, Android users are still on
0.2.7.5.
On Sep 21, 2016 8:30 AM, "teor" wrote:
>
> > On 21 Sep 2016, at 22:46, Tristan wrote:
> >
> > Well, according to this question I asked on Tor's StackExchange, version
> 0.2.4.26 is still technically in the recommen
>>> So, how do we get tor to move past 100-200Mbit? Is it just a waiting game?
I'd say just run more instances if you still have resources left and
want to contribute more bw.
(obviously also your exit policy influences on how much your instance is
used)
>> How long has the relay been up?
>
> 4
> On 22 Sep 2016, at 05:41, nusenu wrote:
>
So, how do we get tor to move past 100-200Mbit? Is it just a waiting game?
>
> I'd say just run more instances if you still have resources left and
> want to contribute more bw.
> (obviously also your exit policy influences on how much your insta
12 matches
Mail list logo
