I'm using redis only for session caching. But others would use it for static page caching or caching lists and other heavily used static items.
For now I'd start with the basics and just get a different database regardless of which server it runs on. 3000 users is not, but isn't that large. I'm assuming you'd be able to run pretty well on one server. Jim On Apr 4, 2017 8:54 AM, "Áureo Dias Neto" <[email protected]> wrote: It's interesting to think about this possibility ... I'm thinking of something around 3 thousand users, but transactions can vary a lot, since I can have 10 or 1000 users online .. I did not measure this detail right .. How to configure Redis server for caching? And if I keep a single server for the bank and the application itself, what is the best cache practice? -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/web2py/tpzYF1Rh0kY/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
