Is this solution still working out for you? I’d really like to implement something similar.
I reviewed the trac and didn’t see this anywhere, has this fallen off the to do list or am I overlooking something. I would love to see this in the core.
I’ve stepped it down to a maximum of 5 rows with a 1 second delay, but am not seeing improvement.
So I’ve migrated 250k topics, and am working on the replies right now. The topics went fairly quickly (a couple hours at 100 rows every 3-5 sec), but the reply import is going dreadfully slow. I stepped the number of rows to process down to 25 and am crawling along at <1 reply per second. I need to import 2.5M replies, so at this rate it will take me 29 days! Help! There has got to be some optimization that can occur.
I’m in the process of importing from XenForo as we speak and have an open ticket regarding a similar timeout. I’m working on migrating about 290k topics and 2.5M posts. The conversion process seems to breeze through users and topics/threads, but has a really tough time with replies/posts. I was able to convert all users and topics using the 100 row limit and a 1 second delay, but I found that in order to proceed with reply imports and not time out or over-tax my database server, I had to step the row limit down to 10 rows with a 1 second delay. I’ve got a 8 GB database server, and it is using about 6 GB of ram right now, so it is working very hard to keep up. I suggest you try lowering your row limit until you start seeing progress again.
Import stopped part way through. Can I resume from where it left off or do I have to do a clean start?
Disregard, I have discovered the issue. I was attempting to do a migration test run by importing the content to a local machine. The problem was that the host IP called out in my config file is a ServiceNet IP which my local machine doesn’t have access to. Using the public address wouldn’t work either because that is not what XenForo uses. So, I instead took the plunge and began migration from one of my network servers to the other, using the ServiceNet IP and was successful. Import appears to be working fine.
