fe1b2dfb4b
Reading from the cidsdb is responsible for about 25% of the runtime of an import. Since the cidmap is used to store the same information in ram, the cidsdb is not written to during an import any longer. And so, if it started off empty (and updateFromLog wasn't needed), those reads can just be skipped. This is kind of a cheesy optimisation, since after any import from any special remote, the database will no longer be empty, so it's a single use optimisation. But it's probably not uncommon to start by importing a lot of files, and it can save a lot of time then. Sponsored-by: Brock Spratlen on Patreon |
||
|---|---|---|
| .. | ||
| Chunked | ||
| AWS.hs | ||
| Chunked.hs | ||
| Encryptable.hs | ||
| ExportImport.hs | ||
| Git.hs | ||
| Hooks.hs | ||
| Http.hs | ||
| Messages.hs | ||
| P2P.hs | ||
| ReadOnly.hs | ||
| Special.hs | ||
| Ssh.hs | ||
| ThirdPartyPopulated.hs | ||