#8856 HIGH Not Tri: 8.2-767: Using Write for actual collaboration slows down writing as well as switching between activities

[Zarro Boogs per Child]

#8856: 8.2-767: Using Write for actual collaboration slows down writing as well as
switching between activities
----------------------------------------+-----------------------------------
   Reporter:  joe                       |       Owner:  Collabora    
       Type:  defect                    |      Status:  new          
   Priority:  high                      |   Milestone:  Not Triaged  
  Component:  write-activity (abiword)  |     Version:  not specified
 Resolution:                            |    Keywords:               
Next_action:  communicate               |    Verified:  0            
  Blockedby:                            |    Blocking:               
----------------------------------------+-----------------------------------

Comment(by gregorio):

 Hi Tomeu,

 Thanks for the decode of the logs. Can you associate this with the master
 memory tracking bug? I forget which one that is but it looks related.

 Do you think it would be useful to do a write collaboration scale test
 with just write running?

 My take is that should help separate the memory issue from multiple
 activities vs. write using too much memory vs. high scale collaboration
 taking too much memory.

 FYI on how many activities 8.2 is supposed to support. I said "generally
 not more than 3" in the 8. release notes at:
 http://wiki.laptop.org/go/Release_Notes/8.2.0#Notable_open_bugs_in_this_release

 Thanks,

 Greg S

-- 
Ticket URL: <http://dev.laptop.org/ticket/8856#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system