Hi bentonsmith,
Sorry that you ran into issues here!
When you’re doing the import, our CSV importer should be able to handle far more than 4000 listings per entry, but that depends entirely on your server’s hardware settings and capabilities.
Imports are very memory-intensive, so it can’t hold all of the records in memory at once, it must periodically save them and this is what ultimately limits the speed of import.
Are you running shared hosting? If so, you may see extremely slow import times because of the memory limits they impose.
You might ask if your web host can increase those limits while you complete your import to speed things along.
Running on shared hosting with that kind of data load in general will lead to problems in the long run. If you want that kind of data, you really need to migrate to something a bit more powerful to handle the data queries you need, like a VPS or dedicated server. Shared hosting simply cannot handle 700K records with any level of competency.
We don’t have “direct SQL import” because we have to call the WordPress API and create posts from each line. That’s how we build the data structures WordPress expects for a custom post type.
Thanks for the quick reply.
Yes I am on a VPS (which I suppose is shared hosting in a way) – I will increase the number of imports and see how that goes.
I did not realize you create a post for each import 🙁 now I see why you dont have a SQL import facility
Thanks once again
