http://www.curse-gaming.com/ - if you get a white page its because it
can't hit the SQL server :)
This was a complete recode of our site to use the Django platform.
Everything from the news system and wiki to the forums and files
hosting. We also have a video section and several other major features
in the works :)
On Dec 10, 11:30 pm, "Jeremy Dunck" <jdu...@gmail.com> wrote:
> > This was a complete recode of our site to use the Django platform.Congratulations, and keep pushing on Django's performance. You're
> making everyone faster. ;-)
We also redid the session system to run completely off memcached, as
this was the real killer for the database.
The site's now nearly stable and should have a very high traffic period
next month so we'll see how things go :)
I guess volatile session data is OK, or do you write out sessions from
memcached to disk at intervals?
I'm going to have a similar problem coming up soon and am curious
which route you took.
On Dec 18, 4:42 am, "Jeremy Dunck" <jdu...@gmail.com> wrote:
> > this was the real killer for the database.I guess volatile session data is OK, or do you write out sessions from
On 12/18/06, dcr...@gmail.com <dcr...@gmail.com> wrote:
> It's runing purely off memcached. We have at least 6 memcached servers,
> maybe a few more, and it just updates memcached when the session
This didn't really answer whether volatile session data is OK.
Are you aware that running multiple memcached's results in
partitioning of value storage to multiple machines (based on a hash of
the key) rather than redundant storage of the values?
You obviously know what you're doing-- I'm just pointing it out since
it'd be a subtle problem until one of the memcache's goes down. :)
Well, it was meant to be. :-/
We have set it up, so that it can save the session data in the db as
backup for when we'll need the system to be more reliable.