One additional thing to notice.. on the 'General Information' page you can
see *what* in your machine that causes you to QR.. if a value is closing in
at 100% your node will QR becuase of it.. if one of the time values goes
above, say 0.5 seconds then *it* will cause your node to QR.
Most of the
Nick Tarleton wrote:
I will run a permanent test node, even though I'm on a 33.6k and won't
be
on often. Address is namshub.dyndns.org:4131.
Then you aren't really permanent now, are you ? (tongue in cheek)
The node should be configured as transient really I guess..
Working great. I
I recently upgraded my stable network node from build 6251 to 6281 (+some
committed locking changes that will be in 6282). I am still running the node
on the stable network though.. I haven't noticed an improved browsing
experience really.. but well, my 6281 is fighting a loosing battle against
I'm glad that major routing bug was squashed. Well done! But I think there
is yet one more big thinko somewhere...
It seems that the network is not learning who specializes in what areas of
the keyspace from successful and failed requests. For a number of weeks
now I have been running my node
On October 26, 2003 09:54 pm, Ken Corson wrote:
Okay, this one took me 20 minutes to catch it happening - my node is
rejecting the majority of query requests. And it works like this:
I accept every request for a 'little while' (1 to 2 minutes). Then I
reject every request (for 5 to 20
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv10183/src/freenet
Modified Files:
OpenConnectionManager.java
Log Message:
Lesser optimization
Index: OpenConnectionManager.java
===
RCS
On October 27, 2003 02:36 am, Tracy R Reed wrote:
I'm glad that major routing bug was squashed. Well done! But I think there
is yet one more big thinko somewhere...
It seems that the network is not learning who specializes in what areas of
the keyspace from successful and failed requests. For
--- Martin Stone Davis [EMAIL PROTECTED] wrote:
In any case, I think this thread is complete... Toad's premix routing
solution (when he's able to get to it) will solve the anonymity problems
I raised.
Don't want to reil anyone up but..
Long term if we implement something like premix
Some Guy wrote:
Long term if we implement something like premix routing, we could
change the underlieing network to some more efficient DHT as long as
it was secure against DSA and other censorship attacks dirrected at
the data.
I have never seen any convincing argument that a DHT will perform
--- Nick Tarleton [EMAIL PROTECTED] wrote:
I have heard a lot about Freenet's emergent behavior and would like to
understand just what mechanisms in the code make this happen.
I'll do my best to answer these guys for you.
1. How does specialization occur? Specifically, how does a new
--- Ian Clarke [EMAIL PROTECTED] wrote:
Some Guy wrote:
Long term if we implement something like premix routing, we could
change the underlieing network to some more efficient DHT as long as
it was secure against DSA and other censorship attacks dirrected at
the data.
I have never
Update of /cvsroot/freenet/freenet/src/freenet/crypt
In directory sc8-pr-cvs1:/tmp/cvs-serv24701/src/freenet/crypt
Modified Files:
Yarrow.java
Added Files:
ThrottledAsyncEntropyYarrow.java
Log Message:
Unfinalized Yarrow.
Added another version of the Yarrow PRNG.
--- NEW FILE:
(no heavy mathspeak in this one)
It seems that there are two differing expectations about how
the datastore can specialize. Perhaps a visual representation
of keyspace can help what I'm saying -
1) . . . . . ..-=*###*==--... . .. .
2) . . -*#*-. . ..-+-
--- Ken Corson [EMAIL PROTECTED] wrote:
(no heavy mathspeak in this one)
It seems that there are two differing expectations about how
the datastore can specialize. Perhaps a visual representation
of keyspace can help what I'm saying -
1) . . . . . ..-=*###*==--... . .
--- Tracy R Reed [EMAIL PROTECTED] wrote:
It seems that the network is not learning who specializes in what areas of
the keyspace from successful and failed requests. For a number of weeks
now I have been running my node with a specially tuned datastore. I wrote
a script to delete keys
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv4061/src/freenet
Modified Files:
Ticker.java
Log Message:
Smaller locking scope
Index: Ticker.java
===
RCS file:
Update of /cvsroot/freenet/freenet/src/freenet/node/states/maintenance
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/maintenance
Modified Files:
Checkpoint.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/fs/dir
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/fs/dir
Modified Files:
NativeFSDirectory.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core private and
Update of /cvsroot/freenet/freenet/src/freenet/session
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/session
Modified Files:
FnpLink.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core private and started
Update of /cvsroot/freenet/freenet/src/freenet/presentation
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/presentation
Modified Files:
FreenetProtocol.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core
Update of /cvsroot/freenet/freenet/src/freenet/node/states/request
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/request
Modified Files:
Pending.java InsertPending.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/client
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/client
Modified Files:
ClientCore.java InternalClient.java FNPClient.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet
Modified Files:
DSAAuthentity.java Core.java ConnectionHandler.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core
Update of /cvsroot/freenet/freenet/src/freenet/support/servlet/http
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/support/servlet/http
Modified Files:
HttpServletRequestImpl.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/node/states/FCP
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/FCP
Modified Files:
NewGenerateSVKPair.java NewClientPut.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Update of /cvsroot/freenet/freenet/src/freenet/message
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/message
Modified Files:
NodeMessage.java DataSend.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core
Update of /cvsroot/freenet/freenet/src/freenet/node/states/FNP
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/FNP
Modified Files:
FNPFeedbackToken.java NewRequest.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/client/http
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/client/http
Modified Files:
ContextManager.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core private
Update of /cvsroot/freenet/freenet/src/freenet/support/test
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/support/test
Modified Files:
FieldsTest.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core private
Update of /cvsroot/freenet/freenet/src/freenet/node/states/data
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/data
Modified Files:
SendData.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core
Update of /cvsroot/freenet/freenet/src/freenet/node/states/announcing
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/announcing
Modified Files:
Announcing.java NewInitialRequest.java SendAnnouncement.java
Log Message:
Work around problem with
Update of /cvsroot/freenet/freenet/src/freenet/support
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/support
Modified Files:
FileBucket.java TempBucketFactory.java CryptBucket.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/node/http
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/http
Modified Files:
DistributionServlet.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made randSource in Core private
Update of /cvsroot/freenet/freenet/src/freenet/crypt
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/crypt
Modified Files:
Yarrow.java DiffieHellman.java
ThrottledAsyncEntropyYarrow.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow
Update of /cvsroot/freenet/freenet/src/freenet/node/states/announcement
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node/states/announcement
Modified Files:
NewAnnouncement.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow initialization order.
Made
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv5586/src/freenet/node
Modified Files:
Node.java LoadStats.java Main.java NodeConsole.java
ConnectionOpener.java
Log Message:
Work around problem with ThrottleAsyncEntropyYarrow/Yarrow
Update of /cvsroot/freenet/freenet/src/freenet/client/http
In directory sc8-pr-cvs1:/tmp/cvs-serv9925/src/freenet/client/http
Modified Files:
NodeStatusServlet.java
Log Message:
improve nodestatus page with last estimate. make 6280 mandatory.
Index: NodeStatusServlet.java
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv9925/src/freenet
Modified Files:
Version.java
Log Message:
improve nodestatus page with last estimate. make 6280 mandatory.
Index: Version.java
Update of /cvsroot/freenet/freenet/src/freenet/node/rt
In directory sc8-pr-cvs1:/tmp/cvs-serv9925/src/freenet/node/rt
Modified Files:
NodeEstimator.java StandardNodeEstimator.java
Log Message:
improve nodestatus page with last estimate. make 6280 mandatory.
Index: NodeEstimator.java
Update of /cvsroot/freenet/freenet/src/freenet
In directory sc8-pr-cvs1:/tmp/cvs-serv12430/src/freenet
Modified Files:
PeerPacketMessage.java
Log Message:
Use a pool of ByteArrayOutputStream:s instead of keeping one single static one, avoid
quite evil blocking of other threads.
Index:
Ken Corson [EMAIL PROTECTED] writes:
(no heavy mathspeak in this one)
It seems that there are two differing expectations about how
the datastore can specialize. Perhaps a visual representation
of keyspace can help what I'm saying -
1) . . . . . ..-=*###*==--... . .
Ed Tomlinson [EMAIL PROTECTED] writes:
Note that just because you have your DS with lots of 'A's in it does not mean
your node is specialized on 'A'.
I agree with this completely, and hope more people understand this point.
What it should do it influence it to specialize
near 'A' (now
On Mon, Oct 27, 2003 at 07:16:40AM -0500, Ed Tomlinson spake thusly:
Think the routing bug could easily have caused this. Think about it. We
we using the worst path. So data would follow this. Once a node got
Yes, I agree. However I am concerned that I am not even seeing signs of
recovery
hi all,
I was running a 6281 node and in past three days anything was right
(well, a little slow...)
This evening I updated to 6282 and now my node is still overloaded
(i.e. current estimated load is still near 100.0%)
I don't know if this can be a problem, or if you are interested in it
at
Could someone please explain this 'lesser optimization' to me? Is that
'blockedConnections.put' not important? This change seems to remove it
completely. Won't this blow up if Integer==Null?
Sorry in advance for sticking my eyes in stuff I don't normally follow.
Subject: [freenet-CVS]
On Monday 27 October 2003 01:55 pm, Aureliano Rama wrote:
hi all,
I was running a 6281 node and in past three days anything was right
(well, a little slow...)
This evening I updated to 6282 and now my node is still overloaded
(i.e. current estimated load is still near 100.0%)
I don't know
On October 27, 2003 11:22 am, Edgar Friendly wrote:
Ed Tomlinson [EMAIL PROTECTED] writes:
Note that just because you have your DS with lots of 'A's in it does not
mean your node is specialized on 'A'.
I agree with this completely, and hope more people understand this point.
What it
On October 27, 2003 03:21 pm, Tom Kaitchuck wrote:
On Monday 27 October 2003 01:55 pm, Aureliano Rama wrote:
hi all,
I was running a 6281 node and in past three days anything was right
(well, a little slow...)
This evening I updated to 6282 and now my node is still overloaded
(i.e.
Oct 27, 2003 3:33:50 PM (freenet.node.rt.DecayingRunningAverage, YThread-328,
ERROR): Implausible report: 8216905.0
java.lang.Exception: debug
at
freenet.node.rt.DecayingRunningAverage.report(DecayingRunningAverage.java:37)
at
On Saturday 25 October 2003 02:42 pm, Martin Stone Davis wrote:
Nick Tarleton wrote:
On Thursday 16 October 2003 10:11 am, Martin Stone Davis wrote:
D'oh!!! I goofed: Node C would see that it takes node A LESS TIME to
find keys K101-K1000 than to find keys K1-K100, since A is trying to
hide
On Friday 24 October 2003 11:56 am, Toad wrote:
http://freenet.teitel.net:/servlet/nodestatus/noderefs.txt
- Returns -1 bytes.
And has also, apparently, gone to unstable. How do you return -1 bytes anyway?
--
I love deadlines. I love the whooshing sound they make as they go by.
-
On Sunday 26 October 2003 10:59 am, Tracy R Reed wrote:
On Sun, Oct 26, 2003 at 02:08:20PM +0100, Niklas Bergh spake thusly:
I am pretty sure that toad will do this for any coming stable builds.
Hopefully stable releases will be re-indroduced soon :)
But please, let's not make the same
On Sunday 26 October 2003 03:06 pm, you wrote:
On Sunday 26 October 2003 01:27 pm, Nick Tarleton wrote:
I will run a permanent test node, even though I'm on a 33.6k and won't be
on often. Address is namshub.dyndns.org:4131.
Working great. I already have the first CHK (No, you are NOT
This just turned up in my Connections page:
TypeLocal portPeer ..etc
out-4blahFred,0.6,1.47,6281
What's port -4 when it's at home? That's the only one on the page. Is it
just port 65532 but formatted stoopid?
But I also got two INBOUND connections showing port
On Mon, 2003-10-27 at 18:20, Dave Hooper wrote:
This just turned up in my Connections page:
TypeLocal portPeer ..etc
out-4blahFred,0.6,1.47,6281
What's port -4 when it's at home? That's the only one on the page. Is it
just port 65532 but formatted
On Monday 27 October 2003 07:54 am, Some Guy wrote:
--- Nick Tarleton [EMAIL PROTECTED] wrote:
I have heard a lot about Freenet's emergent behavior and would like to
understand just what mechanisms in the code make this happen.
I'll do my best to answer these guys for you.
1. How does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tracy R Reed wrote:
| On Sun, Oct 26, 2003 at 02:08:20PM +0100, Niklas
Bergh spake thusly:
|
|I am pretty sure that toad will do this for any
coming stable builds.
|Hopefully stable releases will be re-indroduced soon
:)
|
|
| But please, let's not
On Monday 27 October 2003 02:08 am, Niklas Bergh wrote:
Then you aren't really permanent now, are you ? (tongue in cheek)
The node should be configured as transient really I guess..
I have thought this too, as a low-uptime, low-bandwidth node either will hurt
the network or never be used, at
On Sun, Oct 26, 2003 at 03:45:27PM -0500, Nick Tarleton wrote:
On Saturday 25 October 2003 02:42 pm, Martin Stone Davis wrote:
Nick Tarleton wrote:
On Thursday 16 October 2003 10:11 am, Martin Stone Davis wrote:
D'oh!!! I goofed: Node C would see that it takes node A LESS TIME to
find
On Mon, Oct 27, 2003 at 01:18:14PM +0100, Some Guy wrote:
--- Martin Stone Davis [EMAIL PROTECTED] wrote:
In any case, I think this thread is complete... Toad's premix routing
solution (when he's able to get to it) will solve the anonymity problems
I raised.
Don't want to reil anyone
On Mon, Oct 27, 2003 at 06:41:52PM -0500, Nick Tarleton wrote:
On Monday 27 October 2003 02:08 am, Niklas Bergh wrote:
Then you aren't really permanent now, are you ? (tongue in cheek)
The node should be configured as transient really I guess..
I have thought this too, as a low-uptime,
On Sat, Oct 25, 2003 at 11:08:47PM +0200, Max Moritz Sievers wrote:
Hi,
I suggested [1] to add a shortcut in KDE's Konqueror [2] so that one can copy
an URI in the form of freenet:Key/... in the addressfield and then it
is changed into http://localhost:/Key/... .
Thiago Macieira
On Sat, Oct 25, 2003 at 11:08:47PM +0200, Max Moritz Sievers wrote:
Hi,
I suggested [1] to add a shortcut in KDE's Konqueror [2] so that one can copy
an URI in the form of freenet:Key/... in the addressfield and then it
is changed into http://localhost:/Key/... .
Thiago Macieira
On Mon, Oct 27, 2003 at 01:54:16PM +0100, Some Guy wrote:
--- Nick Tarleton [EMAIL PROTECTED] wrote:
I have heard a lot about Freenet's emergent behavior and would like to
understand just what mechanisms in the code make this happen.
I'll do my best to answer these guys for you.
Key
On Mon, Oct 27, 2003 at 08:49:34AM -0500, Ken Corson wrote:
(no heavy mathspeak in this one)
It seems that there are two differing expectations about how
the datastore can specialize. Perhaps a visual representation
of keyspace can help what I'm saying -
1) . . . . .
In case anyone's wondering how the Big Animal Head project is coming along
[EMAIL PROTECTED],yuCNX5UUQUgbRNv3Ire46w/BigAnimalHead//
Anyone with an index on unstable fancy adding this freesite?
d
___
Devl mailing list
[EMAIL PROTECTED]
On Mon, Oct 27, 2003 at 10:17:10AM -0600, Edgar Friendly wrote:
Ken Corson [EMAIL PROTECTED] writes:
I say datastore specialization doesn't cause anything because it
doesn't affect the routing table (they're both affected by successful
requests at the same time). And since nodes don't route
On Mon, Oct 27, 2003 at 06:38:56PM -0500, Nick Tarleton wrote:
A, the evil inserter, spews inserts of 1MB keys randomly to some nodes, at HTL
25. Z, the evil requestor, requests these keys from some other nodes at HTL
25. The data goes from A along random paths, sits there, and eventually
On Sun, Oct 26, 2003 at 07:59:03AM -0800, Tracy R Reed wrote:
On Sun, Oct 26, 2003 at 02:08:20PM +0100, Niklas Bergh spake thusly:
I am pretty sure that toad will do this for any coming stable builds.
Hopefully stable releases will be re-indroduced soon :)
But please, let's not make the
On Mon, Oct 27, 2003 at 03:39:17PM -0800, Salah Coronya wrote:
I dunno how much more stuff is going into unstable,
multiplexing and
premix routing have been discussed, but I'm not sure
if they'll be
pre-0.6 or post-0.6.
Multiplexing may go in before 0.6. Premix routing definitely won't.
--
On Sat, Oct 25, 2003 at 10:31:26PM -0700, Mike Stump wrote:
Inserts with 6281 feel very slow. A brief comment to YoYo using nim,
and 4:38 later it finished. I could have sent it by hand to 11,120
nodes myself in that time if I had connections open to them all, as my
uplink wasn't in use,
On Sat, Oct 25, 2003 at 11:00:54PM -0700, Mike Stump wrote:
Could we have these thread classes:
freenet.node.states.data.DataStateInitiator 12
freenet.node.states.data.TrailerWriteCallbackMessage:true:true9
folded into NIO style stuff and get rid of the need for
Update of /cvsroot/freenet/freenet/src/freenet/node
In directory sc8-pr-cvs1:/tmp/cvs-serv2495
Modified Files:
LoadStats.java
Log Message:
Changed mode line so emacs won't use tabs at all.
Reindented and eliminated all tabs.
Index: LoadStats.java
I'm seeing this same behavior on Windows 2000, using the latest Sun JVM.
Philip Bock
Ian Clarke wrote:
Glad to hear it is better. What operating system and JVM are you using,
and how are you running Freenet? Some JVMs default to only 64MB of
memory which really isn't sufficient for Freenet.
Found this on the Frost boards, and decided to post it, since the problem
was discussed on this board some time ago. Removed the attached original
article, since it was already posted here.
And yes, there is still a problem in unstable, because
1) My node hasn't shown any kind of specialization
On Mon, Oct 27, 2003 at 02:21:36PM -0600, Tom Kaitchuck wrote:
On Monday 27 October 2003 01:55 pm, Aureliano Rama wrote:
hi all,
I was running a 6281 node and in past three days anything was right
(well, a little slow...)
This evening I updated to 6282 and now my node is still
Toad, I think that Niklas knows how to set the protocol version back
down, dude... no need to yell ;-)
--B
On Tue, 10/28/03 at 01:35:52 +, Toad wrote:
On Mon, Oct 27, 2003 at 08:27:02AM +0100, Niklas Bergh wrote:
I recently upgraded my stable network node from build 6251 to 6281 (+some
On Tue, Oct 28, 2003 at 01:40:34AM +, Toad spake thusly:
How exactly did the script work? The store directories are not based on
the beginning of the key, which is used for specialization purposes.
I iterate over every keyfile in the ds, look at the name of the file, and
if I have already
On Monday 27 October 2003 04:30 pm, Ed Tomlinson wrote:
How did you remove the bandwidth limits? If you just commented them out
I think freenet will limit outgoing bandwidth to 10K...
They had been at the defaults. I changed them to 0.
___
Devl
Another possibility: do we want to limit this to files that have had a
certain number of failed requests, for example 2?
This is very interesting, mainly because not only does it give us better
stats, *it gives us more accurate pDNF estimators too!*.
On Tue, Oct 28, 2003 at 02:01:26AM +,
Implementation proposal:
One table, including both old and new failure tables.
Size should be on the order of 50,000 - if this uses significant RAM, it
can probably be optimized significantly.
Each item has:
Key
List of
Hops to live
Time
(this is so that the classic failtable
Here's a crazy idea. I don't know whether this is even possible in Java, but
what if we just had nodes not query reject, and instead had them send a TCP
backoff request to slow incoming queries down so that they are comming in at
the same rate that they are being processed. (With a buffer of
Update of /cvsroot/freenet/freenet/src/freenet/thread
In directory sc8-pr-cvs1:/tmp/cvs-serv19780/src/freenet/thread
Modified Files:
FastThreadFactory.java QThreadFactory.java
Log Message:
6283:
Set new threads to NORMAL priority level. Hopefully this won't fsck up people's
efforts to
On Monday 27 October 2003 07:45 pm, Toad wrote:
Ok, so the proposal:
Keep the current failure table. It should probably be made very large.
Create a large secondary failure table. Keys in this table will still be
routed, but are not counted for statistical purposes, nor do they affect
On Monday 27 October 2003 07:49 pm, Toad wrote:
I'm seeing the same thing. 6281 was fine. 6282 is getting the same number
of queries and rejecting LOTS more.
I think the load values are being skewed. I have removed both bandwith
limits, there are plenty of threads available, and my cpu
On Mon, Oct 27, 2003 at 09:24:00PM -0600, Tom Kaitchuck wrote:
On Monday 27 October 2003 07:45 pm, Toad wrote:
Ok, so the proposal:
Keep the current failure table. It should probably be made very large.
Create a large secondary failure table. Keys in this table will still be
routed,
Update of /cvsroot/freenet/freenet/src/freenet/thread
In directory sc8-pr-cvs1:/tmp/cvs-serv27580
Modified Files:
FastThreadFactory.java
Log Message:
Set the priority before starting the thread.
Index: FastThreadFactory.java
On Mon, Oct 27, 2003 at 09:32:42PM -0600, Tom Kaitchuck wrote:
On Monday 27 October 2003 07:49 pm, Toad wrote:
I'm seeing the same thing. 6281 was fine. 6282 is getting the same number
of queries and rejecting LOTS more.
I think the load values are being skewed. I have removed both
Please do this for QThreadFactory too.
On Mon, Oct 27, 2003 at 07:59:02PM -0800, Pascal wrote:
Update of /cvsroot/freenet/freenet/src/freenet/thread
In directory sc8-pr-cvs1:/tmp/cvs-serv27580
Modified Files:
FastThreadFactory.java
Log Message:
Set the priority before starting the
Toad [EMAIL PROTECTED] writes:
Caching data is just an optimization designed to cut down the work on
the network by having repeated requests travel shorter distances.
Caching is also vital for plausible deniability. And it means there is
no source node - improving anonymity and attack
On Monday 27 October 2003 09:58 pm, Toad wrote:
It would use a lot of RAM, and if we implemented TUKs we would never have
to request keys that did not exist in the first place. TUKs have other
advantages too. IE: Frost would only need to make a very small fraction
of the requests it does
Update of /cvsroot/freenet/freenet/src/freenet/client/http
In directory sc8-pr-cvs1:/tmp/cvs-serv4015/freenet/src/freenet/client/http
Modified Files:
NodeStatusServlet.java
Log Message:
Version.java 6284
Fix bug in LoadStats.java decayingTimeWeightedAverage.
Put this node's average
Update of /cvsroot/freenet/freenet/src/freenet/node/http/infolets
In directory sc8-pr-cvs1:/tmp/cvs-serv4015/freenet/src/freenet/node/http/infolets
Modified Files:
GeneralInfolet.java
Log Message:
Version.java 6284
Fix bug in LoadStats.java decayingTimeWeightedAverage.
Put this node's
LoadStats.java was also changed, but the message is delayed.
-- Ed Huff
---BeginMessage---
Your mail to 'cvs' with the subject
[freenet-CVS] freenet/src/freenet/node LoadStats.java,1.36,1.37
Main.java,1.282,1.283 Node.java,1.232,1.233
Is being held until the list moderator can review it
On Monday 27 October 2003 10:20 pm, Edgar Friendly wrote:
Toad [EMAIL PROTECTED] writes:
Caching data is just an optimization designed to cut down the work on
the network by having repeated requests travel shorter distances.
Caching is also vital for plausible deniability. And it means
A bit ago toad went through all the code and added timeouts to all the
the waits. His commit notes included:
apparently wait() can occasionally block forever on certain current
JVMs. So always use the form with an argument.
Don't use wait() anywhere, as the JVM has sadly been demonstrated to
96 matches
Mail list logo
