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

[WordPress Trac]

#6369: Blogger importer inefficient handling of data
--------------------------+----------------------------
 Reporter:  barry         |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  WordPress.org
Component:  Import        |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+----------------------------

Comment (by Workshopshed):

 Users have reported issues with large blog imports e.g. 1000+ posts, 5000+
 comments in that it stops or slows down this could be a problem with
 memory starvation and/or performance of the database.

 See http://core.trac.wordpress.org/ticket/4010#comment:27

 Yes, the importer is storing keys (partial URL) for each post and comment.
 The key is something like this
 '/feeds/417730729915399755/posts/default/8397846992898424746'

 As Otto mentions, it should be possible to change this from being stored
 in an array and add meta data.

 The posts already add a meta data entry "blogger_permalink", this would
 also need to be added to the comments to support nesting.

 Given that the load of the comments is sequential by post rather than
 random then having them look up the post ID via the DB should not add a
 significant overhead and the performance advantage of not storing the
 comments and posts arrays in the option may compensate for this.

 The CommentEntry class in comment-entry would need to be updated to
 include the meta data.

 The import_comments and import_posts functions in blogger-importer.php
 would need to be updated to remove the use of the arrays.

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