Signalcrest
← Back to feed
lobstersweb

How Gnutella Scaled to Handle Query Traffic

Gnutella scales

Emerging

18

signal score

Too early

trajectory — needs a few more hourly snapshots

Why this scored 18

every term, weighted
Velocity+6.6 / 40 max

Engagement per hour, normalized against the fastest item on its own source

Acceleration+2.2 / 25 max

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25 max

How many independent communities are talking about the same entity

Recency+9.6 / 10 max

Decays to zero over 14 days

Saturation penalty0.3 / 30 max

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite18.2

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement. Full methodology

Signal history

7-day window (free)

Entities

gnutella
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/lob%3A4kp1wg)](https://www.signalcrest.app/topic/lob%3A4kp1wg)

Drop this in a README or blog post — it updates automatically as the score moves.