Skip to content
Signalcrest
Back to feed
stackoverflowdata

MariaDB query is much faster when using CAST() on bound parameters?

Using CAST on bound parameters can noticeably speed up MariaDB queries.

Steady
Signal score
18
Trajectory
Steady
7-day est. ~12

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.2 / 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.1 / 10

Decays to zero over 14 days

Saturation penalty0.9 / 30

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

Composite18.4

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

~12

range 024

14-day

~5

range 020

30-day

~0

range 019

Signal history

7-day window (free)
873

projected trajectory (estimate, not a guarantee)

Entities

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

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