Slow cloning. About more than 8/9 hours for simple site?

Hi @jayr88 – do you by chance have large media libraries on the sites you’ve tried to clone? 25-40k DB records shouldn’t take anywhere close to 8 hrs. There aren’t any special settings that others are using, much faster cloning is just normal behavior for the plugin so there must be something unique about your site or environment.

I have a similar problem with 280k rows in logs i see the plugin insert 1 row every minutes

479.9523s ? PRELOADING rows for wp_options with query:SELECT wp_options.* FROM wp_options WHERE option_id > 262 ORDER BY option_id ASC LIMIT 250
479.9530s ? PRELOADED 250 rows for wp_options
479.9744s ? INSERTING 1 rows into wp_43_options

Inserting one row at a time can be caused by two things:

1. A low max_allowed_packet size for your database server, or
2. One or more database records with a REALLY long string value.

Do you know if either of those could be the case on your site?

I have this max_allowed_packet = 32M

@jarlisteo thanks! But i have allowed max packet on 128M on this server.
@neversettle most of my clients make use of WPbakery or visual composer, so the post_content field is in general big datafield.

For now i have this as output:

End Time: 2020-03-06 00:52:11
Total Time: 1000 min. 45 sec.
Source Site: SOUNDOFCONFETTI
Target Site: SOUNDOFCONFETTI
Tables: 45 items processed
Rows: 37685 items processed
Files: 7670 items processed
Replacements: 18212 replacements made

Are there any things to speed this up in future?

Any other advise? I cant wait 14 hours cloning

I bought pro and same results

Found a solution for this and already put in place while corresponding privately – just posting here for future reference by anyone else with the same issue.

The problem was caused by having a very high baseline memory usage (above 120MB) and a high custom memory limit that was taking effect correctly but not able to be recognized by ini_get().

In this case, a custom memory limit can be defined with the following snippet:

function ns_custom_memory_limit( $exceeded ) {
	$usage = memory_get_usage( true );
	return $usage > 256 * 10000000; // 256 MB
}

add_filter( 'ns_cloner_tables_process_memory_exceeded', 'ns_custom_memory_limit' );
add_filter( 'ns_cloner_rows_process_memory_exceeded', 'ns_custom_memory_limit' );
add_filter( 'ns_cloner_files_process_memory_exceeded', 'ns_custom_memory_limit' );