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

[Jody Harris]

This raised it's ugly head in last night's backup. Fortunately, the symptom
showed up on the very last upload, so I found the timing data on the first
file in the list.

I will attempt to attach a PDF of the timings page to this message. If there
is a ticket for this, or a ticket this should be attached to, let me know.

jody
----
- Think carefully.
- coram Deo
- Credo ut intelligam - "I believe that I may know" (St. Augustin of Hippo)


On Mon, Mar 8, 2010 at 10:54 PM, Jody Harris <imhavoc at gmail.com> wrote:

> On Mon, Mar 8, 2010 at 9:35 PM, Zooko O'Whielacronx <zookog at gmail.com>wrote:
>
>> On Mon, Mar 8, 2010 at 2:01 PM, Brian Warner <warner at lothar.com> wrote:
>> > I've identified a O(n**2) CPU/string-allocation misbehavior in Foolscap
>> > when receiving large strings. This could explain the memory and CPU
>> > problems in Tahoe storage servers when you're uploading large mutable
>> > files to them (where "large" means segments that are more than about
>> > 10MB, which for the default 3-of-10 means filesizes above 30MB). In
>> > particular, uploading a 100MB mutable file at 3-of-10, leading to 33MB
>> > blocks, appears to take about three minutes to unpack, using 100MB in
>> > the process (on each server).
>>
>> So this could explain Jody Harris's CPU-usage problem (reported in
>> this thread), since he uses mutable files for his backups. Jody, was
>> the "largish" file that you were uploading mutable? What was its size
>> (order of magnitude)?
>>
>> Yes, the parameters are in line. Mutable files of the approximate size
> that the symptoms occur.
>
>
>> This would also explain Stott's report of CPU-usage problem when
>> uploading a large mutable file in the initial problem report of #962
>>
>> > I still don't have an explanation for reports of slowdowns and large
>> > memory consumption for large *immutable* files.
>>
>> What reports?
>>
>> > http://foolscap.lothar.com/trac/ticket/149 has some more details. The
>> > fix for this will be inside Foolscap's receive-side token parser, and
>> > Tahoe won't even notice.
>>
>> Do you think we can try to get this foolscap fix into Ubuntu Lucid?
>>
>> Hm, it looks like this might be related to #383. (See also #327.)
>>
>> Regards,
>>
>> Zooko
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100318/71de3c17/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tahoe-slow_store.pdf
Type: application/pdf
Size: 46321 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100318/71de3c17/attachment.pdf>