Seed relay fetches plain overviews by default
Test and deploy / test (push) Successful in 1m6s
Test and deploy / deploy (push) Successful in 1m43s

For 2026 a.b.ath articles Eweka's gzip replies have a long tail (p90 12.4 s
per 20k vs 3.9 s plain; 6.1k vs 10.5k headers/s). SEED_NNTP_COMPRESS turns
compression back on; plain replies are deflated for nodes asynchronously.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Daan MeijerandClaude Opus 5.5 committed 2026-10-06 15:49:21 +02:00
1 parent 7893876435
commit 3e6b5bed56
5 files changed
+21 -5

No files matched your search

+3 -2
View File
@@ -31,7 +31,8 @@ class SeedFetchPool {
}
/**
* A failure is retried once without compression, on a connection of its
* Pooled connections fetch compressed only with SEED_NNTP_COMPRESS (plain is
* faster for recent articles). A failure is retried once without compression, on a connection of its
* own: either the pooled connection was dead (dropped while idle), or the
* server stalled mid-reply in compressed mode. Eweka does that for some
* chunks: it stops after most of the stream and never sends the rest
@@ -105,7 +106,7 @@ class SeedFetchPool {
if (this.open < this.size) {
this.open++
try {
return { client: await this.connect(true), usedAt: Date.now() }
return { client: await this.connect(indexerConfig.seed.nntpCompress), usedAt: Date.now() }
} catch (error) {
this.open--
this.waiters.shift()?.()