Signalcrest
← Back to feed
devtodata

TimescaleDB 2.27 Added Bloom Filters to UPDATE and DELETE. Your EXPLAIN Won't Tell You If They Work Unless You Know These Counters.

TimescaleDB update improves performance

Steady

19

signal score

as of 1d ago

🔗 3

sources · postgres

Cooling

7-day est. ~0

Why this scored 19

every term, weighted
Velocity+3.9 / 40 max

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

Acceleration+0.0 / 25 max

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

Cross-source spread+5.6 / 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.2 / 30 max

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

Composite18.7

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

Outlook

low confidence · estimate, not a guarantee

7-day

~0

range 00

14-day

~0

range 00

30-day

~0

range 00

Signal history

7-day window (free)

— — projected trajectory (estimate, not a guarantee)

Entities

timescaledbpostgres
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/dev%3A4281954)](https://www.signalcrest.app/topic/dev%3A4281954)

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