WriteFreely scaling help
WriteFreely scaling help
@info Yeah, definitely think splitting up the table could make sense, if I can figure out what lines to do that along.
I don't have Redis in place, but am using Varnish on the frontend, which has generally helped reduce database load across the system -- it's just that this blog in particular can still run slow.
Always the hardest part with DB design, segmenting records.
If you have traffic stats on what gets the most requests? It could be a scenario where the most recent material stays in the main or live table(s), for kind of obvious reasons.
The older but high activity segments get their own table(s) with some advance caching.
Low traffic / nobody ever looks at it? Archive. Not worth the bandwidth or overhead.
