WordPress is not capable of handling our 76 MB MT export file, and it can't import the post_id's we need for redirects to work.
So we have to migrate via MySql script.
I need some help writing it. This is what I have so far:
INSERT INTO wp_posts (id, Post_title, post_name, Post_content, post_author, post_date) SELECT entry_id, entry_title, entry_basename, CONCAT(entry_text,entry_text_more) AS post_text, entry_author_id, entry_created_on FROM mises_blog..mt_entry We need to migrate posts, authors, and comments, maintaining the primary keys.
On Sun, Feb 28, 2010 at 3:07 AM, David Veksler <her...@gmail.com> wrote: > I need some DBA help with our blog migration.
> WordPress is not capable of handling our 76 MB MT export file, and it can't > import the post_id's we need for redirects to work.
> So we have to migrate via MySql script.
> I need some help writing it. This is what I have so far:
> INSERT INTO wp_posts > (id, Post_title, post_name, Post_content, post_author, post_date) > SELECT > entry_id, entry_title, entry_basename, CONCAT(entry_text,entry_text_more) > AS post_text, entry_author_id, entry_created_on FROM mises_blog..mt_entry > We need to migrate posts, authors, and comments, maintaining the primary > keys.
> WordPress is not capable of handling our 76 MB MT export file, and it can't > import the post_id's we need for redirects to work.
> So we have to migrate via MySql script.
> I need some help writing it. This is what I have so far:
> INSERT INTO wp_posts > (id, Post_title, post_name, Post_content, post_author, post_date) > SELECT > entry_id, entry_title, entry_basename, CONCAT(entry_text,entry_text_more) > AS post_text, entry_author_id, entry_created_on FROM mises_blog..mt_entry > We need to migrate posts, authors, and comments, maintaining the primary > keys.
Both. It doesn't support importing the postID and it quits (with a success message) before importing all the posts.
Also I am convinced that PHP is the worst language/framework today. It is glacially slow and it considers (according to the documentation) 5MB is a "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's taking forever using 1% of CPU and 15MB of memory.
On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote: > When you say "Wordpress isn't capable", is it because of the size of > the data or something else? > /PEZ
> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > > I need some DBA help with our blog migration.
> > WordPress is not capable of handling our 76 MB MT export file, and it > can't > > import the post_id's we need for redirects to work.
> > So we have to migrate via MySql script.
> > I need some help writing it. This is what I have so far:
> > INSERT INTO wp_posts > > (id, Post_title, post_name, Post_content, post_author, post_date) > > SELECT > > entry_id, entry_title, entry_basename, > CONCAT(entry_text,entry_text_more) > > AS post_text, entry_author_id, entry_created_on FROM mises_blog..mt_entry > > We need to migrate posts, authors, and comments, maintaining the primary > > keys.
Have you tried editing php.ini to allow for > 5MB of memory to be allocated by a script? Or if it is something with max upload size. Or both. Does it still quit without importing anything?
On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: > Both. It doesn't support importing the postID and it quits (with a success > message) before importing all the posts. > Also I am convinced that PHP is the worst language/framework today. It is > glacially slow and it considers (according to the documentation) 5MB is a > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's > taking forever using 1% of CPU and 15MB of memory.
This is probably my doing - we need to maintain legacy links from the main site. If you find an article from 5 years ago, it's blog link takes you directly to the comment box. This is why this is important.
> Have you tried editing php.ini to allow for > 5MB of memory to be > allocated by a script? Or if it is something with max upload size. Or > both. Does it still quit without importing anything?
> /PEZ
> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: > > Both. It doesn't support importing the postID and it quits (with a > success > > message) before importing all the posts. > > Also I am convinced that PHP is the worst language/framework today. It is > > glacially slow and it considers (according to the documentation) 5MB is a > > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's > > taking forever using 1% of CPU and 15MB of memory.
<jeffrey.a.tuc...@gmail.com> wrote: > This is probably my doing - we need to maintain legacy links from the main > site. If you find an article from 5 years ago, it's blog link takes you > directly to the comment box. This is why this is important.
>> Have you tried editing php.ini to allow for > 5MB of memory to be >> allocated by a script? Or if it is something with max upload size. Or >> both. Does it still quit without importing anything?
>> /PEZ
>> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: >> > Both. It doesn't support importing the postID and it quits (with a >> > success >> > message) before importing all the posts. >> > Also I am convinced that PHP is the worst language/framework today. It >> > is >> > glacially slow and it considers (according to the documentation) 5MB is >> > a >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's >> > taking forever using 1% of CPU and 15MB of memory.
>> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>> >> When you say "Wordpress isn't capable", is it because of the size of >> >> the data or something else? >> >> /PEZ
>> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >> >> > I need some DBA help with our blog migration.
>> >> > WordPress is not capable of handling our 76 MB MT export file, and it >> >> > can't >> >> > import the post_id's we need for redirects to work.
>> >> > So we have to migrate via MySql script.
>> >> > I need some help writing it. This is what I have so far:
>> >> > INSERT INTO wp_posts >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) >> >> > SELECT >> >> > entry_id, entry_title, entry_basename, >> >> > CONCAT(entry_text,entry_text_more) >> >> > AS post_text, entry_author_id, entry_created_on FROM >> >> > mises_blog..mt_entry >> >> > We need to migrate posts, authors, and comments, maintaining the >> >> > primary >> >> > keys.
> Have you tried editing php.ini to allow for > 5MB of memory to be > allocated by a script? Or if it is something with max upload size. Or > both. Does it still quit without importing anything?
> /PEZ
> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: > > Both. It doesn't support importing the postID and it quits (with a > success > > message) before importing all the posts. > > Also I am convinced that PHP is the worst language/framework today. It is > > glacially slow and it considers (according to the documentation) 5MB is a > > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's > > taking forever using 1% of CPU and 15MB of memory.
> On Sun, Feb 28, 2010 at 8:44 PM, Jeffrey Tucker > <jeffrey.a.tuc...@gmail.com> wrote: > > This is probably my doing - we need to maintain legacy links from the > main > > site. If you find an article from 5 years ago, it's blog link takes you > > directly to the comment box. This is why this is important.
> >> Have you tried editing php.ini to allow for > 5MB of memory to be > >> allocated by a script? Or if it is something with max upload size. Or > >> both. Does it still quit without importing anything?
> >> /PEZ
> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > wrote: > >> > Both. It doesn't support importing the postID and it quits (with a > >> > success > >> > message) before importing all the posts. > >> > Also I am convinced that PHP is the worst language/framework today. It > >> > is > >> > glacially slow and it considers (according to the documentation) 5MB > is > >> > a > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and > it's > >> > taking forever using 1% of CPU and 15MB of memory.
> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> >> >> When you say "Wordpress isn't capable", is it because of the size of > >> >> the data or something else? > >> >> /PEZ
> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > >> >> > I need some DBA help with our blog migration.
> >> >> > WordPress is not capable of handling our 76 MB MT export file, and > it > >> >> > can't > >> >> > import the post_id's we need for redirects to work.
> >> >> > So we have to migrate via MySql script.
> >> >> > I need some help writing it. This is what I have so far:
> >> >> > INSERT INTO wp_posts > >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) > >> >> > SELECT > >> >> > entry_id, entry_title, entry_basename, > >> >> > CONCAT(entry_text,entry_text_more) > >> >> > AS post_text, entry_author_id, entry_created_on FROM > >> >> > mises_blog..mt_entry > >> >> > We need to migrate posts, authors, and comments, maintaining the > >> >> > primary > >> >> > keys.
On Sun, Feb 28, 2010 at 9:23 PM, David Veksler <her...@gmail.com> wrote: > #Change upload limits > memory_limit 540M > post_max_size 330M > upload_max_filesize 320M > max_execution_time 60000 > #Change upload limits end > It quits after 800 posts. S > --- > Regards, > David V.
>> Have you tried editing php.ini to allow for > 5MB of memory to be >> allocated by a script? Or if it is something with max upload size. Or >> both. Does it still quit without importing anything?
>> /PEZ
>> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: >> > Both. It doesn't support importing the postID and it quits (with a >> > success >> > message) before importing all the posts. >> > Also I am convinced that PHP is the worst language/framework today. It >> > is >> > glacially slow and it considers (according to the documentation) 5MB is >> > a >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's >> > taking forever using 1% of CPU and 15MB of memory.
>> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>> >> When you say "Wordpress isn't capable", is it because of the size of >> >> the data or something else? >> >> /PEZ
>> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >> >> > I need some DBA help with our blog migration.
>> >> > WordPress is not capable of handling our 76 MB MT export file, and it >> >> > can't >> >> > import the post_id's we need for redirects to work.
>> >> > So we have to migrate via MySql script.
>> >> > I need some help writing it. This is what I have so far:
>> >> > INSERT INTO wp_posts >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) >> >> > SELECT >> >> > entry_id, entry_title, entry_basename, >> >> > CONCAT(entry_text,entry_text_more) >> >> > AS post_text, entry_author_id, entry_created_on FROM >> >> > mises_blog..mt_entry >> >> > We need to migrate posts, authors, and comments, maintaining the >> >> > primary >> >> > keys.
> >> Have you tried editing php.ini to allow for > 5MB of memory to be > >> allocated by a script? Or if it is something with max upload size. Or > >> both. Does it still quit without importing anything?
> >> /PEZ
> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > wrote: > >> > Both. It doesn't support importing the postID and it quits (with a > >> > success > >> > message) before importing all the posts. > >> > Also I am convinced that PHP is the worst language/framework today. It > >> > is > >> > glacially slow and it considers (according to the documentation) 5MB > is > >> > a > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and > it's > >> > taking forever using 1% of CPU and 15MB of memory.
> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> >> >> When you say "Wordpress isn't capable", is it because of the size of > >> >> the data or something else? > >> >> /PEZ
> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > >> >> > I need some DBA help with our blog migration.
> >> >> > WordPress is not capable of handling our 76 MB MT export file, and > it > >> >> > can't > >> >> > import the post_id's we need for redirects to work.
> >> >> > So we have to migrate via MySql script.
> >> >> > I need some help writing it. This is what I have so far:
> >> >> > INSERT INTO wp_posts > >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) > >> >> > SELECT > >> >> > entry_id, entry_title, entry_basename, > >> >> > CONCAT(entry_text,entry_text_more) > >> >> > AS post_text, entry_author_id, entry_created_on FROM > >> >> > mises_blog..mt_entry > >> >> > We need to migrate posts, authors, and comments, maintaining the > >> >> > primary > >> >> > keys.
On Sun, Feb 28, 2010 at 9:39 PM, David Veksler <her...@gmail.com> wrote: > It doesn't return any errors. > All timeouts are off. > --- > Regards, > David V.
>> >> Have you tried editing php.ini to allow for > 5MB of memory to be >> >> allocated by a script? Or if it is something with max upload size. Or >> >> both. Does it still quit without importing anything?
>> >> /PEZ
>> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> >> >> wrote: >> >> > Both. It doesn't support importing the postID and it quits (with a >> >> > success >> >> > message) before importing all the posts. >> >> > Also I am convinced that PHP is the worst language/framework today. >> >> > It >> >> > is >> >> > glacially slow and it considers (according to the documentation) 5MB >> >> > is >> >> > a >> >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and >> >> > it's >> >> > taking forever using 1% of CPU and 15MB of memory.
>> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>> >> >> When you say "Wordpress isn't capable", is it because of the size of >> >> >> the data or something else? >> >> >> /PEZ
>> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >> >> >> > I need some DBA help with our blog migration.
>> >> >> > WordPress is not capable of handling our 76 MB MT export file, and >> >> >> > it >> >> >> > can't >> >> >> > import the post_id's we need for redirects to work.
>> >> >> > So we have to migrate via MySql script.
>> >> >> > I need some help writing it. This is what I have so far:
>> >> >> > INSERT INTO wp_posts >> >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) >> >> >> > SELECT >> >> >> > entry_id, entry_title, entry_basename, >> >> >> > CONCAT(entry_text,entry_text_more) >> >> >> > AS post_text, entry_author_id, entry_created_on FROM >> >> >> > mises_blog..mt_entry >> >> >> > We need to migrate posts, authors, and comments, maintaining the >> >> >> > primary >> >> >> > keys.
> Which version of Wordpress are you using? 2.9.2? I think I'll give > that import a try myself.
> /PEZ
> On Sun, Feb 28, 2010 at 9:39 PM, David Veksler <her...@gmail.com> wrote: > > It doesn't return any errors. > > All timeouts are off. > > --- > > Regards, > > David V.
> >> > 2010/2/28 Peter Strömberg <p...@pezius.com>
> >> >> Why must the postID be kept?
> >> >> Have you tried editing php.ini to allow for > 5MB of memory to be > >> >> allocated by a script? Or if it is something with max upload size. Or > >> >> both. Does it still quit without importing anything?
> >> >> /PEZ
> >> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > >> >> wrote: > >> >> > Both. It doesn't support importing the postID and it quits (with > a > >> >> > success > >> >> > message) before importing all the posts. > >> >> > Also I am convinced that PHP is the worst language/framework today. > >> >> > It > >> >> > is > >> >> > glacially slow and it considers (according to the documentation) > 5MB > >> >> > is > >> >> > a > >> >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and > >> >> > it's > >> >> > taking forever using 1% of CPU and 15MB of memory.
> >> >> > --- > >> >> > Regards, > >> >> > David V.
> >> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> >> >> >> When you say "Wordpress isn't capable", is it because of the size > of > >> >> >> the data or something else? > >> >> >> /PEZ
> >> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > >> >> >> > I need some DBA help with our blog migration.
> >> >> >> > WordPress is not capable of handling our 76 MB MT export file, > and > >> >> >> > it > >> >> >> > can't > >> >> >> > import the post_id's we need for redirects to work.
> >> >> >> > So we have to migrate via MySql script.
> >> >> >> > I need some help writing it. This is what I have so far:
> Importing now. Using stock 2.9.2 import so it probably doesn't honor > the ID:s, but I should be able to patch the script for that. So far > 2120 entries imported. I don't know how many there are to import and > it's getting late here so I'll leave my MacBook on and see if it has > finished when I wake up.
> /PEZ
> On Sun, Feb 28, 2010 at 9:50 PM, David Veksler <her...@gmail.com> wrote: >> Yes, please do. >> --- >> Regards, >> David V.
>>> Which version of Wordpress are you using? 2.9.2? I think I'll give >>> that import a try myself.
>>> /PEZ
>>> On Sun, Feb 28, 2010 at 9:39 PM, David Veksler <her...@gmail.com> wrote: >>> > It doesn't return any errors. >>> > All timeouts are off. >>> > --- >>> > Regards, >>> > David V.
>>> >> > 2010/2/28 Peter Strömberg <p...@pezius.com>
>>> >> >> Why must the postID be kept?
>>> >> >> Have you tried editing php.ini to allow for > 5MB of memory to be >>> >> >> allocated by a script? Or if it is something with max upload size. >>> >> >> Or >>> >> >> both. Does it still quit without importing anything?
>>> >> >> /PEZ
>>> >> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> >>> >> >> wrote: >>> >> >> > Both. It doesn't support importing the postID and it quits (with >>> >> >> > a >>> >> >> > success >>> >> >> > message) before importing all the posts. >>> >> >> > Also I am convinced that PHP is the worst language/framework >>> >> >> > today. >>> >> >> > It >>> >> >> > is >>> >> >> > glacially slow and it considers (according to the documentation) >>> >> >> > 5MB >>> >> >> > is >>> >> >> > a >>> >> >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 >>> >> >> > and >>> >> >> > it's >>> >> >> > taking forever using 1% of CPU and 15MB of memory.
>>> >> >> > --- >>> >> >> > Regards, >>> >> >> > David V.
>>> >> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>>> >> >> >> When you say "Wordpress isn't capable", is it because of the size >>> >> >> >> of >>> >> >> >> the data or something else? >>> >> >> >> /PEZ
>>> >> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >>> >> >> >> > I need some DBA help with our blog migration.
>>> >> >> >> > WordPress is not capable of handling our 76 MB MT export file, >>> >> >> >> > and >>> >> >> >> > it >>> >> >> >> > can't >>> >> >> >> > import the post_id's we need for redirects to work.
>>> >> >> >> > So we have to migrate via MySql script.
>>> >> >> >> > I need some help writing it. This is what I have so far:
Importing now. Using stock 2.9.2 import so it probably doesn't honor the ID:s, but I should be able to patch the script for that. So far 2120 entries imported. I don't know how many there are to import and it's getting late here so I'll leave my MacBook on and see if it has finished when I wake up.
>> Which version of Wordpress are you using? 2.9.2? I think I'll give >> that import a try myself.
>> /PEZ
>> On Sun, Feb 28, 2010 at 9:39 PM, David Veksler <her...@gmail.com> wrote: >> > It doesn't return any errors. >> > All timeouts are off. >> > --- >> > Regards, >> > David V.
>> >> > 2010/2/28 Peter Strömberg <p...@pezius.com>
>> >> >> Why must the postID be kept?
>> >> >> Have you tried editing php.ini to allow for > 5MB of memory to be >> >> >> allocated by a script? Or if it is something with max upload size. >> >> >> Or >> >> >> both. Does it still quit without importing anything?
>> >> >> /PEZ
>> >> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> >> >> >> wrote: >> >> >> > Both. It doesn't support importing the postID and it quits (with >> >> >> > a >> >> >> > success >> >> >> > message) before importing all the posts. >> >> >> > Also I am convinced that PHP is the worst language/framework >> >> >> > today. >> >> >> > It >> >> >> > is >> >> >> > glacially slow and it considers (according to the documentation) >> >> >> > 5MB >> >> >> > is >> >> >> > a >> >> >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 >> >> >> > and >> >> >> > it's >> >> >> > taking forever using 1% of CPU and 15MB of memory.
>> >> >> > --- >> >> >> > Regards, >> >> >> > David V.
>> >> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>> >> >> >> When you say "Wordpress isn't capable", is it because of the size >> >> >> >> of >> >> >> >> the data or something else? >> >> >> >> /PEZ
>> >> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >> >> >> >> > I need some DBA help with our blog migration.
>> >> >> >> > WordPress is not capable of handling our 76 MB MT export file, >> >> >> >> > and >> >> >> >> > it >> >> >> >> > can't >> >> >> >> > import the post_id's we need for redirects to work.
>> >> >> >> > So we have to migrate via MySql script.
>> >> >> >> > I need some help writing it. This is what I have so far:
Importing post Unpromising start to Becker-Posner Blog... Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in .../wp-includes/plugin.php on line 302
Going to bed. But this should be fixable if we split the import file up some.
> Importing post Results of M ndliche Pr fung, Mises University, Session > Two, 2004...
> Doesn't look right, what's the charset/encoding used in the MT install?
> /PEZ
> 2010/2/28 Peter Strömberg <p...@pezius.com>: >> Importing now. Using stock 2.9.2 import so it probably doesn't honor >> the ID:s, but I should be able to patch the script for that. So far >> 2120 entries imported. I don't know how many there are to import and >> it's getting late here so I'll leave my MacBook on and see if it has >> finished when I wake up.
>> /PEZ
>> On Sun, Feb 28, 2010 at 9:50 PM, David Veksler <her...@gmail.com> wrote: >>> Yes, please do. >>> --- >>> Regards, >>> David V.
>>>> Which version of Wordpress are you using? 2.9.2? I think I'll give >>>> that import a try myself.
>>>> /PEZ
>>>> On Sun, Feb 28, 2010 at 9:39 PM, David Veksler <her...@gmail.com> wrote: >>>> > It doesn't return any errors. >>>> > All timeouts are off. >>>> > --- >>>> > Regards, >>>> > David V.
>>>> >> > 2010/2/28 Peter Strömberg <p...@pezius.com>
>>>> >> >> Why must the postID be kept?
>>>> >> >> Have you tried editing php.ini to allow for > 5MB of memory to be >>>> >> >> allocated by a script? Or if it is something with max upload size. >>>> >> >> Or >>>> >> >> both. Does it still quit without importing anything?
>>>> >> >> /PEZ
>>>> >> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> >>>> >> >> wrote: >>>> >> >> > Both. It doesn't support importing the postID and it quits (with >>>> >> >> > a >>>> >> >> > success >>>> >> >> > message) before importing all the posts. >>>> >> >> > Also I am convinced that PHP is the worst language/framework >>>> >> >> > today. >>>> >> >> > It >>>> >> >> > is >>>> >> >> > glacially slow and it considers (according to the documentation) >>>> >> >> > 5MB >>>> >> >> > is >>>> >> >> > a >>>> >> >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 >>>> >> >> > and >>>> >> >> > it's >>>> >> >> > taking forever using 1% of CPU and 15MB of memory.
>>>> >> >> > --- >>>> >> >> > Regards, >>>> >> >> > David V.
>>>> >> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
>>>> >> >> >> When you say "Wordpress isn't capable", is it because of the size >>>> >> >> >> of >>>> >> >> >> the data or something else? >>>> >> >> >> /PEZ
>>>> >> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: >>>> >> >> >> > I need some DBA help with our blog migration.
>>>> >> >> >> > WordPress is not capable of handling our 76 MB MT export file, >>>> >> >> >> > and >>>> >> >> >> > it >>>> >> >> >> > can't >>>> >> >> >> > import the post_id's we need for redirects to work.
>>>> >> >> >> > So we have to migrate via MySql script.
>>>> >> >> >> > I need some help writing it. This is what I have so far:
I saw the call for help on twitter so I'm stopping by to offer my 2cents. I agree with Peter's suggestion. If the import function inserts one row at a time the process could take longer than the timeout settings in apache and php.ini. Chopping the data into chunks and loading each separately is worth a shot. If that doesn't work I'd try the "LOAD DATA INFILE" method from the command line.
On Feb 28, 3:31 pm, Peter Strömberg <p...@pezius.com> wrote:
> >> Have you tried editing php.ini to allow for > 5MB of memory to be > >> allocated by a script? Or if it is something with max upload size. Or > >> both. Does it still quit without importing anything?
> >> /PEZ
> >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> wrote: > >> > Both. It doesn't support importing the postID and it quits (with a > >> > success > >> > message) before importing all the posts. > >> > Also I am convinced that PHP is the worst language/framework today. It > >> > is > >> > glacially slow and it considers (according to the documentation) 5MB is > >> > a > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and it's > >> > taking forever using 1% of CPU and 15MB of memory.
> >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> >> >> When you say "Wordpress isn't capable", is it because of the size of > >> >> the data or something else? > >> >> /PEZ
> >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > >> >> > I need some DBA help with our blog migration.
> >> >> > WordPress is not capable of handling our 76 MB MT export file, and it > >> >> > can't > >> >> > import the post_id's we need for redirects to work.
> >> >> > So we have to migrate via MySql script.
> >> >> > I need some help writing it. This is what I have so far:
> >> >> > INSERT INTO wp_posts > >> >> > (id, Post_title, post_name, Post_content, post_author, post_date) > >> >> > SELECT > >> >> > entry_id, entry_title, entry_basename, > >> >> > CONCAT(entry_text,entry_text_more) > >> >> > AS post_text, entry_author_id, entry_created_on FROM > >> >> > mises_blog..mt_entry > >> >> > We need to migrate posts, authors, and comments, maintaining the > >> >> > primary > >> >> > keys.
On Sun, Feb 28, 2010 at 6:26 PM, RPG <init...@gmail.com> wrote: > I saw the call for help on twitter so I'm stopping by to offer my > 2cents. I agree with Peter's suggestion. If the import function > inserts one row at a time the process could take longer than the > timeout settings in apache and php.ini. Chopping the data into > chunks and loading each separately is worth a shot. If that doesn't > work I'd try the "LOAD DATA INFILE" method from the command line.
> On Feb 28, 3:31 pm, Peter Strömberg <p...@pezius.com> wrote: > > That's hope in'it? =) How about timeout limits in the web server? Is it > Apache?
> > /PEZ
> > On Sun, Feb 28, 2010 at 9:23 PM, David Veksler <her...@gmail.com> wrote: > > > #Change upload limits > > > memory_limit 540M > > > post_max_size 330M > > > upload_max_filesize 320M > > > max_execution_time 60000 > > > #Change upload limits end > > > It quits after 800 posts. S > > > --- > > > Regards, > > > David V.
> > >> Have you tried editing php.ini to allow for > 5MB of memory to be > > >> allocated by a script? Or if it is something with max upload size. Or > > >> both. Does it still quit without importing anything?
> > >> /PEZ
> > >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > wrote: > > >> > Both. It doesn't support importing the postID and it quits (with a > > >> > success > > >> > message) before importing all the posts. > > >> > Also I am convinced that PHP is the worst language/framework today. > It > > >> > is > > >> > glacially slow and it considers (according to the documentation) 5MB > is > > >> > a > > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and > it's > > >> > taking forever using 1% of CPU and 15MB of memory.
> > >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> > >> >> When you say "Wordpress isn't capable", is it because of the size > of > > >> >> the data or something else? > > >> >> /PEZ
> > >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > > >> >> > I need some DBA help with our blog migration.
> > >> >> > WordPress is not capable of handling our 76 MB MT export file, > and it > > >> >> > can't > > >> >> > import the post_id's we need for redirects to work.
> > >> >> > So we have to migrate via MySql script.
> > >> >> > I need some help writing it. This is what I have so far:
Do you have root access to the server? I ask because I think it's time to start changing settings in php.ini to enable the export functions of MT and the import functions of WP to have enough time to complete.
> On Sun, Feb 28, 2010 at 6:26 PM, RPG <init...@gmail.com > <mailto:init...@gmail.com>> wrote:
> I saw the call for help on twitter so I'm stopping by to offer my > 2cents. I agree with Peter's suggestion. If the import function > inserts one row at a time the process could take longer than the > timeout settings in apache and php.ini. Chopping the data into > chunks and loading each separately is worth a shot. If that doesn't > work I'd try the "LOAD DATA INFILE" method from the command line.
> On Feb 28, 3:31 pm, Peter Str mberg <p...@pezius.com > <mailto:p...@pezius.com>> wrote: > > That's hope in'it? =) How about timeout limits in the web > server? Is it Apache?
> > /PEZ
> > On Sun, Feb 28, 2010 at 9:23 PM, David Veksler <her...@gmail.com > <mailto:her...@gmail.com>> wrote: > > > #Change upload limits > > > memory_limit 540M > > > post_max_size 330M > > > upload_max_filesize 320M > > > max_execution_time 60000 > > > #Change upload limits end > > > It quits after 800 posts. S > > > --- > > > Regards, > > > David V.
> > > 2010/2/28 Peter Str mberg <p...@pezius.com > <mailto:p...@pezius.com>>
> > >> Why must the postID be kept?
> > >> Have you tried editing php.ini to allow for > 5MB of memory to be > > >> allocated by a script? Or if it is something with max upload > size. Or > > >> both. Does it still quit without importing anything?
> > >> /PEZ
> > >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler > <her...@gmail.com <mailto:her...@gmail.com>> wrote: > > >> > Both. It doesn't support importing the postID and it > quits (with a > > >> > success > > >> > message) before importing all the posts. > > >> > Also I am convinced that PHP is the worst > language/framework today. It > > >> > is > > >> > glacially slow and it considers (according to the > documentation) 5MB is > > >> > a > > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB > DDR3 and it's > > >> > taking forever using 1% of CPU and 15MB of memory.
> > >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com > <mailto:pez...@gmail.com>> wrote:
> > >> >> When you say "Wordpress isn't capable", is it because of > the size of > > >> >> the data or something else? > > >> >> /PEZ
> > >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com > <mailto:her...@gmail.com>> wrote: > > >> >> > I need some DBA help with our blog migration.
> > >> >> > WordPress is not capable of handling our 76 MB MT export > file, and it > > >> >> > can't > > >> >> > import the post_id's we need for redirects to work.
> > >> >> > So we have to migrate via MySql script.
> > >> >> > I need some help writing it. This is what I have so far:
The link you gave for the export (http://blog.mises.com/ mises_economics_blog.zip ) is returning 404 Not Found.
If PHP/Apache is yielding time-outs maybe the best way is as RPG suggests to use LOAD DATA INFILE (see http://dev.mysql.com/doc/refman/5.1/en/load-data.html). If that fails, then the remedy is as you said to write a SQL script. I have some experience with MySQL (with and without PHP) but not with WordPress. Anyway, if the correspondence between tables/columns is known, it shouldn't be too hard.
So I ask: what is the correspondence between tables/columns?
BTW - In the query which you present, the number of columns in *1, *2 and *3 must be the same, so your query will not work.
INSERT INTO wp_posts (*1) SELECT *2 AS *3 FROM mises_blog..mt_entry
João
On Mar 1, 12:41 am, David Veksler <her...@gmail.com> wrote:
> On Sun, Feb 28, 2010 at 6:26 PM, RPG <init...@gmail.com> wrote: > > I saw the call for help on twitter so I'm stopping by to offer my > > 2cents. I agree with Peter's suggestion. If the import function > > inserts one row at a time the process could take longer than the > > timeout settings in apache and php.ini. Chopping the data into > > chunks and loading each separately is worth a shot. If that doesn't > > work I'd try the "LOAD DATA INFILE" method from the command line.
> > On Feb 28, 3:31 pm, Peter Strömberg <p...@pezius.com> wrote: > > > That's hope in'it? =) How about timeout limits in the web server? Is it > > Apache?
> > > /PEZ
> > > On Sun, Feb 28, 2010 at 9:23 PM, David Veksler <her...@gmail.com> wrote: > > > > #Change upload limits > > > > memory_limit 540M > > > > post_max_size 330M > > > > upload_max_filesize 320M > > > > max_execution_time 60000 > > > > #Change upload limits end > > > > It quits after 800 posts. S > > > > --- > > > > Regards, > > > > David V.
> > > > 2010/2/28 Peter Strömberg <p...@pezius.com>
> > > >> Why must the postID be kept?
> > > >> Have you tried editing php.ini to allow for > 5MB of memory to be > > > >> allocated by a script? Or if it is something with max upload size. Or > > > >> both. Does it still quit without importing anything?
> > > >> /PEZ
> > > >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > > wrote: > > > >> > Both. It doesn't support importing the postID and it quits (with a > > > >> > success > > > >> > message) before importing all the posts. > > > >> > Also I am convinced that PHP is the worst language/framework today. > > It > > > >> > is > > > >> > glacially slow and it considers (according to the documentation) 5MB > > is > > > >> > a > > > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 and > > it's > > > >> > taking forever using 1% of CPU and 15MB of memory.
> > > >> > --- > > > >> > Regards, > > > >> > David V.
> > > >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> > > >> >> When you say "Wordpress isn't capable", is it because of the size > > of > > > >> >> the data or something else? > > > >> >> /PEZ
> > > >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > > > >> >> > I need some DBA help with our blog migration.
> > > >> >> > WordPress is not capable of handling our 76 MB MT export file, > > and it > > > >> >> > can't > > > >> >> > import the post_id's we need for redirects to work.
> > > >> >> > So we have to migrate via MySql script.
> > > >> >> > I need some help writing it. This is what I have so far:
> The link you gave for the export (http://blog.mises.com/ > mises_economics_blog.zip ) is returning 404 Not Found.
> If PHP/Apache is yielding time-outs maybe the best way is as RPG > suggests to use LOAD DATA INFILE (see > http://dev.mysql.com/doc/refman/5.1/en/load-data.html). > If that fails, then the remedy is as you said to write a SQL script. I > have some experience with MySQL (with and without PHP) but not with > WordPress. Anyway, if the correspondence between tables/columns is > known, it shouldn't be too hard.
> So I ask: what is the correspondence between tables/columns?
> BTW - In the query which you present, the number of columns in *1, *2 > and *3 must be the same, so your query will not work.
> INSERT INTO wp_posts (*1) > SELECT *2 AS *3 > FROM mises_blog..mt_entry
> João
> On Mar 1, 12:41 am, David Veksler <her...@gmail.com> wrote: > > I tried that. It's still randomly skipping posts even with 5MB chunks.
> > Also, Movable Type only exported half the posts.
> > On Sun, Feb 28, 2010 at 6:26 PM, RPG <init...@gmail.com> wrote: > > > I saw the call for help on twitter so I'm stopping by to offer my > > > 2cents. I agree with Peter's suggestion. If the import function > > > inserts one row at a time the process could take longer than the > > > timeout settings in apache and php.ini. Chopping the data into > > > chunks and loading each separately is worth a shot. If that doesn't > > > work I'd try the "LOAD DATA INFILE" method from the command line.
> > > On Feb 28, 3:31 pm, Peter Strömberg <p...@pezius.com> wrote: > > > > That's hope in'it? =) How about timeout limits in the web server? Is > it > > > Apache?
> > > > /PEZ
> > > > On Sun, Feb 28, 2010 at 9:23 PM, David Veksler <her...@gmail.com> > wrote: > > > > > #Change upload limits > > > > > memory_limit 540M > > > > > post_max_size 330M > > > > > upload_max_filesize 320M > > > > > max_execution_time 60000 > > > > > #Change upload limits end > > > > > It quits after 800 posts. S > > > > > --- > > > > > Regards, > > > > > David V.
> > > > > 2010/2/28 Peter Strömberg <p...@pezius.com>
> > > > >> Why must the postID be kept?
> > > > >> Have you tried editing php.ini to allow for > 5MB of memory to be > > > > >> allocated by a script? Or if it is something with max upload size. > Or > > > > >> both. Does it still quit without importing anything?
> > > > >> /PEZ
> > > > >> On Sun, Feb 28, 2010 at 8:18 PM, David Veksler <her...@gmail.com> > > > wrote: > > > > >> > Both. It doesn't support importing the postID and it quits > (with a > > > > >> > success > > > > >> > message) before importing all the posts. > > > > >> > Also I am convinced that PHP is the worst language/framework > today. > > > It > > > > >> > is > > > > >> > glacially slow and it considers (according to the documentation) > 5MB > > > is > > > > >> > a > > > > >> > "large" file. I have a sever with RAID1, 16 cores and 6GB DDR3 > and > > > it's > > > > >> > taking forever using 1% of CPU and 15MB of memory.
> > > > >> > On Sun, Feb 28, 2010 at 3:56 AM, PEZ <pez...@gmail.com> wrote:
> > > > >> >> When you say "Wordpress isn't capable", is it because of the > size > > > of > > > > >> >> the data or something else? > > > > >> >> /PEZ
> > > > >> >> On Feb 28, 10:07 am, David Veksler <her...@gmail.com> wrote: > > > > >> >> > I need some DBA help with our blog migration.
> > > > >> >> > WordPress is not capable of handling our 76 MB MT export > file, > > > and it > > > > >> >> > can't > > > > >> >> > import the post_id's we need for redirects to work.
> > > > >> >> > So we have to migrate via MySql script.
> > > > >> >> > I need some help writing it. This is what I have so far:
Under the "Resource Limits" section of your php.ini config file there should be a max_execution_time variable, it is this variable that I would look at first. In a normal "production" environment it should be set just long enough to complete all normal running php processes. It is my guess that the maintenance functions that you are trying to execute are taking much longer than the current setting. As a result of this php kills the process because it is running too long. This is done to avoid overloading the server because of bad script, etc. My guess is that the production value of max_execution_time is set to "30" (seconds), temporary bump that up to "900", restart apache and see if your export/import functions work.
David Veksler wrote: > > Do you have root access to the server? I ask because I think it's > time to start changing settings in php.ini to enable the export > functions of MT and the import functions of WP to have enough time to > complete.
> Yes, there is no configuration value limiting the process. PHP and > Perl are just shitty runtimes not designed to handle real-life data > volumes.
> I attached the schemas for WordPress and Movable Type.
David Veksler <her...@gmail.com> wrote: > Yes, there is no configuration value limiting the process. PHP and Perl are > just shitty runtimes not designed to handle real-life data volumes. [...]
Did you attempt to upload and import in the same operation over HTTP, or did you FTP the MT export to wp-content/mt-export.txt and tell WP to work on local data? The latter is cruising along happily on my little underpowered Vista laptop.
I get that you're frustrated, but spraying ignorant comments doesn't help the situation. I had hoped a similar snipe from another poster the other day was an anomaly.
