Damned Lies current setup consists of two app servers both having a local vcs sandbox (2,5gb each). Both servers run a resource-consuming updatestats.py script on these sandboxes to produce the stats that are hold in two different sqlite databases.
We could use a setup with an "offline" damned lies instance that would only produce the stats and send it to a mysql database. Then two light-weighted DL app servers would serve the website using the mysql database.
We already want to move from sqlite to mysql and reduce the load on the web servers. This way we can achieve both.
If we are to do this, here's a rough plan:
As a backup plan, we can turn the balancer to use only app1, run the last step just with that one, and if everything is ok, do it for app2 and balance it again.
Replying to [comment:1 glezos]:
We already want to move from sqlite to mysql and reduce the load on the web servers. This way we can achieve both. If we are to do this, here's a rough plan: Setup DL on a new app server (say app3). This instance should be off the web and have the cronjob script installed. Get this instance to hit mysql and run the cronjob once to populate it. Remove the cronjob from app1,2 and update them to serve from mysql.
We still need to get or copy the PO/POTs generated from the 'offline' instance though, it's not only the database content that's generated by the update-stats script...
Can we perhaps do this a bit simpler:
1) Set up a mysql user/database for Damned Lies on db1 2) Forward all requests to http://translate.fedoraproject.org/POT/* to the instance running the update-stats script. (traffic is not that heavy and it's only for sharing static files...)
Does this make sense?
This would easy the maintenance a lot as well, not having to debug two update-stats scripts..
I'll be happy to do some testing on this.
Woah this is old :-) Damned Lies is history now :-)
Login to comment on this ticket.