OverviewFilesCommitsIssuesDocsReleasesPeers

wirecore commits / 359d141

Reduce concurrent connections to respect pub.wiredove.net limits
pub.wiredove.net runs a simple Deno file server with no rate limiting or connection pooling. Our 50 concurrent connections were likely overwhelming it, causing hangs and slowdowns. Analysis of pub.wiredove.net: - Simple Deno serveDir() - no connection limits - No rate limiting or backpressure - Just serves static files from disk - Not designed for high concurrent loads Changed maxSockets: 50 → 5 to be respectful of their infrastructure. This may have been causing the wiredove.net slowdowns we observed. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
359d1411b352540edf139a968ba000f9f5f69c2e
by plankatron <fleeky@gmail.com> · 2026-01-20T17:03:04.000Z

Changed files (1) +3 -2

lib/wirecore-apds.js +3 -2
……@@ -13,8 +13,9 @@ import https from 'node:https'
1313import hypercore_crypto from 'hypercore-crypto'
1414import nacl from 'tweetnacl'
1515
16// Increase concurrent HTTP connections limit for blob fetching
17https.globalAgent.maxSockets = 50
16// Limit concurrent connections to avoid overwhelming pub.wiredove.net
17// (it's a simple Deno file server with no rate limiting)
18https.globalAgent.maxSockets = 5
1819
1920let store = null
2021let metaBee = null // For key-value metadata