Skip to content
Signalcrest
Back to feed
stackoverflowdata

Should I create indexes on all columns used in WHERE conditions for a large table?

Indexing every WHERE column may hurt performance; use selective indexing.

Steady
Signal score
18
Trajectory
→ Steady
7-day est. ~17

Why this scored 18

every term, weighted
Velocity+0.0 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+11.1 / 25

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

Cross-source spread+0.0 / 25

How many independent communities are talking about the same entity

Recency+8.2 / 10

Decays to zero over 14 days

Saturation penalty−0.8 / 30

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

Composite18.5

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, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology

Outlook

low confidence · estimate, not a guarantee

7-day

~17

range 0–29

14-day

~15

range 0–30

30-day

~11

range 0–30

Signal history

7-day window (free)
1433

projected trajectory (estimate, not a guarantee)

Entities

mysql
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/so%3A80006459)](https://www.signalcrest.app/topic/so%3A80006459)

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