Steven Zahm@ Jason
Hmmm… large import like this I do breakup into 10K files. The larger the file the larger it takes to import because it has to be parsed each time by the CSV library for each 100 imported.
Now, each new file should start quickly before “settling down” and each file should take about the same amount of time.
So, to clarify, what you’re seeing is each file is taking longer than the preceding one?
Things that can be done to speed up import…
Remove all empty blank columns in the CSV file. For example, if none of the entries you are importing contain a Linkedin profile, delete that column. The fewer the columns, even if empty, the less processing the CSV library has to do.
Install the Code Snippets plugin and add a snippet with following code:
add_action( 'plugins_loaded', 'cn_remove_geocode', 11 );
function cn_remove_geocode() {
remove_filter( 'cn_set_address', array( 'cnEntry_Action', 'geoCode' ) );
}
Each address is sent to Google for geocoding for lat/lng. With this many imported entries they are likely no longer geocoding as they only allow so many within a rolling 24 hour period unless you a Google Maps API Premier subscriber (I think that’s the correct term).
It’s only a fraction of a second per address, but it does add up.
If you want, you can send me you split CSV files and I can do some testing to make sure there is nothing within them that would some be slowing things down.
Oh, which version of the CSV Import are you using? The latest?