About a week ago I said I would set up an unstable node that was deliberately 
firewalled to see if it could be of any use to the network. Here are the 
results.

First I was running unstable at the current version of it. Then when 5031 came 
out I switched to that. I currently have over 300 connections and just over 
100 transmitting data. The number of connections has remained fairly constant 
except after I shut it down to upgrade it. (It does not supprise me that I 
have so many connections transmitting. As there is some external packet 
filtering software which is slowing down individual connections, but Freenet 
overall is running with effectively unlimited bandwidth.)

In any event my node is constantly about 1 stdiv above the network average in 
terms of load, (current 40K QPH) and about a .25 acceptance rate, which from 
what I gather, now a days is above average. And my routing time is typically 
between 10 and 20 ms.

Most notably my node has been able to sustain connections for long periods of 
time. Some of them for nearly the entire uptime of my node, and some with 
several thousand messages transmitted.

Memory useage is excellent. I am seeing extended periods of under 30MB of 
useage. Although I had seen a strange behavior on some previous versions. It 
would load up and function and I could brouse Freenet, come back and check my 
memory useage and it would be something like 40MB. Then it would VERY SLOWLY 
continue to climb ever higher until it got near the limit then the garbage 
collector would activate and that would take it down about 20MB and then that 
process would repeat. I have not yet seen this on 5031.

One other weird thing is that I see a lot of these messages in the log:

Took 1672 seconds to send [EMAIL PROTECTED]:freenet.Message: 
QueryRejected @null @ dbac31a18d9f50: htl=1, reason=Node 
overloaded:QueryRejected{Close=false,Sustain=false,DataLength=0,{HopsToLive=1,Reason=Node
 
overloaded,Attenuation=1,UniqueID=dbac31a18d9f50,}}:null:true, 
prio=1(notifySuccess(null)! (last connection registered 0 seconds ago on 
[EMAIL PROTECTED] (DSA(dcab 87c7 73b4 c208 bf88 57fa 9d09 055d f426 
7c5d),tcp/24.48.81.75:9801, sessions=1, presentations=1, ID=DSA(dcab 87c7 
73b4 c208 bf88 57fa 9d09 055d f426 7c5d)): outbound attempts=22:4/26

I don't know what causes that, but overall I would say it seems to be fairly 
healthy and as far as I can tell contributing to the network. This has not 
been possible to my knowledge until quite recently. So I would say, that as 
long as there is no great harm in doing this, that maybe we should stop 
recomending users that are behind NATs/Firewalls that are out of their 
control to be transient. This is also a good sign in that some of the more 
elaborate measures, such as shadow nodes may be unnecessary. Maybe we should 
just have a firewalled flag so other nodes know not to bother to contact you, 
and let that be the end of it.

_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to