Syncthing Community Forum - Support, announcements, development coordi...

They got back in sync without me doing anything.

Still in garbageCollectBlocklistsAndBlocksLocked. The function aborts after 5 minutes so I wondered how it continued on the next call to periodic.It doesn’t try to remember where it was and simply randomizes the ranges so that there’s a chance to process...

The more I dig the more problems I find.
I saw that garbageCollectBlocklistsAndBlocksLocked attempted to split the table in ranges to process and being hopeful I tried to understand the whole process…
One of the first things it does is count the rows in the table to have a guess as how to split the whole hash range in subranges… This means a whole table scan right from the beginning, not having even anything to process yet....

I’m looking at the rest of db_service.go and there’s some really bad things for large databases in there.
All the garbageCollect* methods basically make full table scans to do their work.
So each time “periodic” is called what is done is a nearly full db read (most if not all large tables are parsed) and it locks the whole DB doing so (the call to fdb.updateLock.Lock())....