Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-09 02:34:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated System Requirements (markdown)

Michael Stanclift 2021-04-06 16:24:26 -05:00
parent c07224a7be
commit e8d700a3d7
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
System-Requirements.md

@ -16,9 +16,19 @@ The main requirement is Gravity Sync requires at least two separate Pi-hole 5.x
### Storage Performance
Pi-hole on its own can be abusive to SD card installs on a Raspberry Pi, due to its constant writes of logging to the disk. Gravity Sync introduces some additional storage overhead to a traditional Pi-hole environment. The replication process of the Domain Database involves performing an MD5 hash of the running database, taking a backup of the running configuration, performing an SQL integrity check, transferring it across the network to a secondary Pi-hole where it is then hashed again after it's put into production to make sure the process completed successfully. Larger databases will also increase the time and increase the risk of failed replication.
Pi-hole on its own can be abusive to SD card installs on a Raspberry Pi, due to its constant writes of logging to the disk. Gravity Sync introduces some additional storage overhead to a traditional Pi-hole environment. The replication process of the Domain Database involves:
It is suggested, that you place your Pi-hole instance on resilient, well performing storage media. If you have failed or inconsistent Gravity Sync replication sessions, this is often the root cause.
- Performing an MD5 hash of the running database
- Taking backups of the running configuration
- Performing an SQL integrity check
- Transferring files across the network
- Further hashing to validate replication
Also the larger your Domain Database is, the increased time it will take to perform these tasks, and perhaps additional risk of corruption due to failed replication.
When using a Raspberry Pi or other similar device as the primary or secondary Pi-hole target, it is suggested that you select well performing storage media. This could be a high quality SD card, but an external flash drive, SSD or even a spinning disk is suggested if available.
If you have failed or inconsistent Gravity Sync replication sessions, that either don't complete the backup or don't pass the integrity check, this is often the root cause.
## Required Components