I wouldn't know. Assuming you're fine with rocket's performances, it should have a lower impact on ram usage. BTW, the default setup with nginx+uwsgi is not heavy at all.
On Wednesday, October 30, 2013 8:52:46 PM UTC+1, Jesus Alvaro wrote: > > I've already found some answers in: > > http://www.web2pyslices.com/slice/show/1384/low-memory-fooprint-using-lighttpd > > in which option B is recomended > > > > > El miércoles, 30 de octubre de 2013 19:04:27 UTC+1, Jesus Alvaro escribió: >> >> Hello >> >> When deploying web2py in a VPS as the only service, what is a better >> minimal option in terms of efficiency/speed?: >> >> A- Use of Rocket (default) server as a daemon (with option -n threads >> ...) >> B- Lighttp+ fcgi (unix socket to a single w2p instance >> >> Let's consider an estimated peak load of 30 simultaneous clients >> Despite of static content and https handling, Is there any advantage in >> using approach B in terms of speed? >> >> >> In a second case of multiple applications, What is better approach? >> C. one w2p instance per application (several ports) >> D a single w2p instance running several applications (just one port) >> >> Any suggestion welcome >> Thanks in advance >> >> >> >> -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
