The current backoff changes seem to be making the problem worse and causing most of the network to be backed off, but it could just be related to different load at different times of day, so we'll give it a while longer.
A proposal to solve the problem: - Do NOT backoff on getting a quick transfer failure (a transfer cancellation). Hence transfer backoff only occurs on the original node. Transfer cancellations are treated as DNFs - they might be malicious, so route the key elsewhere next time. - If a transfer takes more than 15 seconds, send a transfer failure downstream to free up the original request, do transfer backoff on the node, and switch the incoming transfer into "turtle mode". Hence real time requests are fast. - If a turtle mode transfer receives a cancellation, kill it, end of story. (All of the nodes along the chain, except the first one, will do this). - If a turtle mode transfer completes, store it to our datastore and offer it via ULPRs to those who have requested it. Hence if the only node with the data is slow, we still get the data, but slowly, for queued downloads / subscriptions. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090113/77e8522d/attachment.pgp>
