Citat af Marcel Keller mkel...@cs.au.dk:
Indeed we did not know (well I didn't) back then that the data was
not sent immediately by Twisted, and I was starting to think
yesterday whether the hack would make a difference. Lucky for us,
it apparently does :)
That is not the only problem. To free the memory of the shares and
to send out further shares, also the incoming shares must be
processed as soon as possible. This is even trickier because
incoming shares might trigger code that calls functions sending out
data, which activates the Twisted reactor again and therefore leads
to a possibly too deep recursion. I think I have a solution for
that, it just wasn't necessary to implement it for now because the
hack worked anyway.
Ah, but the numbers I had been shown did not indicate we were anywhere
near running out of memory. That's not to say memory isn't important
(it certainly will be in cases with huge amounts of operations), I
just didn't think it had anything to do with our specific test cases
for the paper.
___
viff-devel mailing list (http://viff.dk/)
viff-devel@viff.dk
http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
