IP addresses are NOT logged in this forum so there's no point asking. Please note that this forum is full of homophobes, racists, lunatics, schizophrenics & absolute nut jobs with a smattering of geniuses, Chinese chauvinists, Moderate Muslims and last but not least a couple of "know-it-alls" constantly sprouting their dubious wisdom. If you believe that content generated by unsavory characters might cause you offense PLEASE LEAVE NOW! Sammyboy Admin and Staff are not responsible for your hurt feelings should you choose to read any of the content here.
The OTHER forum is HERE so please stop asking.

Hi Sam, do you consider a temp solution for MYSQL load during GE?

uncleyap · 2011-04-19T05:16:21+00:00

I have several ideas for you to consider: Add a remote SQL server paying for only 2 months at the most. Shift SQL there and back after GE. Off load SQL db temporarily, make a SQL backup now, purge away historic data keeping only the last 2 month's data, and lighten the load, merge back to backup after GE. Add a static mirror, for reading only - can not post, read only, different URL, based in SG, it clones from your real SQL db. divert main traffic here, and only when users hit POST or anything that writes SQL db, that they will be directed to actual server. That mean a kind of quasi reverse-proxy to take the load / hits for READING users. This way lots of readers can read without SQL db errors. ;)

Thread starter uncleyap
Start date Apr 19, 2011

uncleyap

Alfrescian

Loyal

Apr 19, 2011

I have several ideas for you to consider:

Add a remote SQL server paying for only 2 months at the most. Shift SQL there and back after GE.
Off load SQL db temporarily, make a SQL backup now, purge away historic data keeping only the last 2 month's data, and lighten the load, merge back to backup after GE.
Add a static mirror, for reading only - can not post, read only, different URL, based in SG, it clones from your real SQL db. divert main traffic here, and only when users hit POST or anything that writes SQL db, that they will be directed to actual server. That mean a kind of quasi reverse-proxy to take the load / hits for READING users. This way lots of readers can read without SQL db errors.