user19338: I still use bitcoin 0.13.2 for some reasons. Recent mempool size is very high so syncing mempool takes for a long time, over two days. Are there any ways to sync mempool faster? I have some bitcoind nodes. Some of them have already finished to sync full mempool. I hope I can copy mempool from my another nodes.

user5406: As dark knight stated, Bitcoin Core 0.14.0 brought us the feature of persisting the mempool over restarts of Core. I've been also hearing some rumors that there's improved set reconciliation for mempools in the work by some Core developers.

user26481: I had a similar issue where I restarted my bitcoin node for changing some parameters and it took half a day to catch upto to all uncomfirmed tx. Bitcoin 0.14 has a feature that stores current mempool to disk and loads it back on startup https://github.com/bitcoin/bitcoin/pull/8448. It should be possible to copy mempool.dat files to your other nodes that are behind.

19338: <p>I still use bitcoin 0.13.2 for some reasons. Recent mempool size is very high so syncing mempool takes for a long time, over two days. Are there any ways to sync mempool faster? I have some bitcoind nodes. Some of them have already finished to sync full mempool. I hope I can copy mempool from my another nodes.</p>
 5406: <p>As dark knight stated, <a href="https://bitcoin.org/en/release/v0.14.0" rel="nofollow noreferrer">Bitcoin Core 0.14.0</a> brought us the feature of persisting the mempool over restarts of Core. I've been also hearing some rumors that there's improved set reconciliation for mempools in the work by some Core developers.</p>
 26481: <p>I had a similar issue where I restarted my bitcoin node for changing some parameters and it took half a day to catch upto to all uncomfirmed tx. Bitcoin 0.14 has a feature that stores current mempool to disk and loads it back on startup <a href="https://github.com/bitcoin/bitcoin/pull/8448" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/pull/8448</a>. It should be possible to copy mempool.dat files to your other nodes that are behind.</p>
