4 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Opus 5.5	cdc1cdc0cc	Prober: claim only candidates of settled releases, without the join ... The settler marks a settled release's candidates ready (and unreadable when it had no readable name). Claims took the candidates by joining releases from random points of the queue; in its newer half nothing had settled, so a slice scanned to the end (0.3 s each, 20 slices and 5 tiers a claim) and the prober stood still: 2.4M waiting, 0 probed a minute. Now an index over the claimable rows only, the slices drawn within them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 12:12:59 +02:00
Daan MeijerandClaude Opus 5.5	885e4e6541	Settler: history releases settle after half an hour ... A release whose last post is 6 hours old gets nothing from the tail, only fragments from neighbouring ranges: settled once unchanged for 30 minutes. Waiting 6 hours after it was read held every history release back from phase 2 after each reset; with the hourly sweeps' resets the prober (and so the par2 merge) never had work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 09:42:53 +02:00
Daan MeijerandClaude Opus 5.5	0613984de9	Rebuild: re-uploads are releases of their own ... A poster re-uploading under the same name made one release of all uploads: in a sample, 24% of releases with 2+ files had a file name more than once (4.3% of files extra copies), 70% of those copies posted a day or more apart; their NZBs listed each copy. - File assembly keeps a re-upload's copy apart: a part already in every open copy, posted more than 3 h from them, starts another copy; a missing part fills the nearest copy (a re-send of what was missing), a re-sent part near a copy that has it is ignored as before. - A key's files in a batch split into uploads where posting pauses for more than 3 h, counted from the latest article posted so far (a file that takes hours to post doesn't split it); each upload is judged and chunked on its own (ReleaseChunk.upload, .postedLast; candidates carry their upload). - The catalog matches a chunk to the release of its key whose articles the range's group owns and whose posting window is within 3 h, else starts one (key, key:2, …): releases get identity_key, group_id, last_posted_at. Keys are locked in order (advisory locks), so concurrent batches neither deadlock nor both start one; the merger writes in key order too. The same upload multi-posted to other groups is a release per group. - The gap: 91% of uploads post within 3 h; 73% of re-uploaded copies come later (releases:upload-gaps). releases:duplicates measures the duplicate names. Both implementations; check.ts compares the windows and uploads too (identical on all captures; Rust tests mirror the TypeScript cases). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 13:31:35 +02:00
Daan MeijerandClaude Opus 5.5	80c920f678	Rebuild: settling quiet releases ... Hourly in coordinator:run: a release unchanged for 6 hours is settled, complete when every file its [i/N] counter announced was found, unknown without a counter (phase 2 reads par2 sets for those). Partial index on unsettled releases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 02:33:47 +02:00