<p>Chain-index tries to use the existing db file, but if anything goes wrong it just starts over, so it's hard to diagnose. It could be a version difference. Or it could be a silly mistake, but without error it's hard to say.</p>
<p>You could try simple things like running it for a bit on the new machine and copying the file over to the old machine and see if it picks that up.</p>

CC BY-SA 4.0
2022-02-02T14:17:13.593Z
Thanks for the answer and yes, it is a differen't version of chain-index that I am trying to bootstrap, so most likely that is what the issue is.
lley154
CC BY-SA 4.0
2022-02-01T10:18:39.640Z
2022-02-01T10:18:39.640Z
Sjoerd Visscher
<p>It seems, that syncing chain-index.db is faster on a Linux in a Windows Subsystem for Linux (WSL2) than in a standalone Linux. This might be caused of a better virtual memory manager on Windows or some special compiled-in kernel features.</p>
<p>On my Windows 11 Home / WSL2 Ubuntu-20.04 system with 16 GB RAM and AMD Ryzen 5 3500U 2.10 GHz processor and SSD, syncing on 2022-04-20 took <em>about 14 hours</em>.</p>
<p>Kernel version of my WSL2 (<em>uname -r</em>): <code>5.4.72-microsoft-standard-WSL2</code> of 2021-06-07, see <a href="https://www.catalog.update.microsoft.com/Search.aspx?q=Windows%20Subsystem%20for%20Linux%20Update" rel="nofollow noreferrer">Kernel Updates</a>.</p>

CC BY-SA 4.0
2022-06-02T16:31:31.517Z
2023-03-11T16:12:49.950Z
2023-03-11T16:12:49.950Z
burdie
<p>The process to sync the plutus-pab chain-index for the testnet takes over 3+ days now and will take longer as time goes on.   Is it possible to bootstrap the chain-index sync process to reduce the manual sync process?  I've tried copying over the chain-index.db (and referencing that file in the chain-index-config.json  file) that was already sync'd from another machine, but it appears to be starting over again. Thank you.</p>

CC BY-SA 4.0
2022-01-31T11:30:34.523Z
Copying over chain-index.db should work. What exacly are you running on the command line?
Sjoerd Visscher
CC BY-SA 4.0
2022-01-31T17:04:10.323Z
Thanks for confirming.   The command I am running is from the plutus-pab/test-node readme.   cabal exec -- plutus-chain-index --config testnet/chain-index-config.json start-index.
lley154
<plutus-pab>
bootstrap chain-index.db
# bootstrap chain-index.db

(Asked by: username_0 on 2022-01-31)

The process to sync the plutus-pab chain-index for the testnet takes over 3+ days now and will take longer as time goes on. Is it possible to bootstrap the chain-index sync process to reduce the manual sync process? I've tried copying over the chain-index.db (and referencing that file in the chain-index-config.json file) that was already sync'd from another machine, but it appears to be starting over again. Thank you.

**Tags:** plutus-pab
> **Comments:**
> **username_1**: Copying over chain-index.db should work. What exacly are you running on the command line?  
> **username_0**: Thanks for confirming.   The command I am running is from the plutus-pab/test-node readme.   cabal exec -- plutus-chain-index --config testnet/chain-index-config.json start-index.  

---

## 2 answers

### Answer by username_1 on 2022-02-01. Score: 0

Chain-index tries to use the existing db file, but if anything goes wrong it just starts over, so it's hard to diagnose. It could be a version difference. Or it could be a silly mistake, but without error it's hard to say.

You could try simple things like running it for a bit on the new machine and copying the file over to the old machine and see if it picks that up.

> **Comments:**
> **username_0**: Thanks for the answer and yes, it is a differen't version of chain-index that I am trying to bootstrap, so most likely that is what the issue is.  

---

### Answer by username_2 on 2022-06-02. Score: 0

It seems, that syncing chain-index.db is faster on a Linux in a Windows Subsystem for Linux (WSL2) than in a standalone Linux. This might be caused of a better virtual memory manager on Windows or some special compiled-in kernel features.

On my Windows 11 Home / WSL2 Ubuntu-20.04 system with 16 GB RAM and AMD Ryzen 5 3500U 2.10 GHz processor and SSD, syncing on 2022-04-20 took *about 14 hours*.

Kernel version of my WSL2 (*uname -r*): `5.4.72-microsoft-standard-WSL2` of 2021-06-07, see [Kernel Updates](https://www.catalog.update.microsoft.com/Search.aspx?q=Windows%20Subsystem%20for%20Linux%20Update).


---

