> Why are inserts so slow? > Well, inserts visit more nodes. This means: > a) They take longer, (quite a lot longer) and
a) They do, but I don't agree that we cant send more packets. > b) They are more likely to get a RejectedOverload (or a timeout). b) agreed, but that is obviously not the Problem. If I can insert in an exact Intervall of 15 seconds none of them seem to dropped anywhere. So each tried insert does work, but they are much too far apart. I'll probably checkout the insert-source tomorrow. (for a more technical reaction) Right now I dont know exaclty how an insert work. 1 Phase (starting sending Data immediatly to possible node) or 2 Phases (searching a chain, and sending along the chain)? the Packets are much smaller now, I hope 1 Phase is used. Especially since the Incoming packets are not the problem normally in asynchrnous connections. In My Case (one outgoing connection) I could and I should send as much data as I can as long as the other node doesn't complain about it. And the server doesnt complain (he is quite idle), he is well connected to other nodes, so he can send at max speed aswell. This means as soon as a block is completly sent the next block must start the next transfer (not necessary my insert, but data). If the node can't do that I waste nearly 94% of my connection, and we all know that uploadbandwith limits most of the users, and if freenet cant at least use the limited upload, an insert will be still horrible. I give you a comparison: If I insert a VideoCD around 600 MB, with my uploadaspeed I can up it in around 6 hours, right now it would take 3.75 Days. Thats the kind of difference the user WILL notice. The darknet is not very crowded at the moment, there are not many timeouts, what do you think if freenet 0.7 grows to the state of 0.5? the inserts wont get faster in such an enviroment.
