[wp-trac] [WordPress Trac] #6369: Blogger importer inefficient handling of data

[WordPress Trac]

#6369: Blogger importer inefficient handling of data
---------------------+------------------------------------------------------
 Reporter:  barry    |       Owner:  anonymous
     Type:  defect   |      Status:  new      
 Priority:  normal   |   Milestone:  2.7      
Component:  General  |     Version:           
 Severity:  normal   |    Keywords:           
---------------------+------------------------------------------------------
 If the import dataset is large, the Blogger importer can store huge
 amounts of data in the blogger_importer option.  It then updates this data
 over and over throughout the import. If MySQL logging (binary or query) is
 enabled, this can result in a large amount of data being written to disk,
 potentially filling up the partition rather quickly.  On WordPress.com, I
 have seen an import write 100MB of binary logs every 2 min.  Andy's
 suggestion is that we split up the data from the import rather than store
 it in one option.  This would allow us to manipulate it more granularly
 and prevent the huge updates from happening.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/6369>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software