> In summary: > - It was enough to create something like namespaces for Cache (global, > sessionkeys, session1, session2, ...) > - Add Cache sharing with other nodes. > - It is difficult to predict the size of the session thus the demand for > cache size.
When I first started using uwsgi I was planning to simply store session objects in a global(ish) python dictionary and message little microbatches of changes between application servers. It's potentially a way to go. Caveat hacker: eventual consistency. Personally, I've just gone fully database-backed. Nginx -> uwsgi -> mongodb lets me run six queries and spit out a json reply in 5ms or so on my cluster of bottom-range VPS accounts. Whatfor should I (or anybody else) break my back over half a millisecond of request time? Only if it's the last thing left on the bug list. -Schmidty _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
