[tahoe-dev] 1.6.0 When storing shares (from another machine), Python consumes --> 100% of local (storage node) CPU

[David-Sarah Hopwood]

Zooko O'Whielacronx wrote:
> On Thursday, 2010-03-18, at 7:37 , Jody Harris wrote:
>> [...]
> 
> Thanks for the bug report! This is #983. I guess I should have Cc:'ed
> you on that ticket since your earlier report was part of the process
> of finding the bug.
> 
> This is actually my highest Tahoe-LAFS-hacking priority right now, and
> the way I've been going about it is to write up this "StringChain"
> package which I hope could be used to fix this problem. That's pretty
> much done (footnote 1), and the next step is for me to write a patch
> and off it to Brian for foolscap #149. (I'm not sure that StringChain
> is the right way to fix foolscap #149 and I suspect Brian is even less
> sure, but it is worth a try.)
> 
> I'm hoping to get a fixed foolscap into Ubuntu Lucid so that Lucid
> users don't have this problem.
> 
> In the meantime, the work-around is not to use mutable files and to
> keep your mutable directories nice and small.

Sssh, don't convince Jody not to use mutable files -- how else would we
find the bugs in them? ;-)

(Seriously, Jody's bug reports have been very helpful.)

> Immutable files perform
> much better than mutable files do, for this reason (#983) as well as a
> few other reasons. They also have the handy property that they are
> immutable, so you can be sure that the file contents have not changed.
> Another problem with mutable files is that they break the FTP and SFTP
> frontends (#680, #941).

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
Url : http://allmydata.org/pipermail/tahoe-dev/attachments/20100318/bdb6897c/attachment.pgp