The built-in server is fast, as fast if not faster than apache but it has other limitations: - slow on static files copared to apache - size limit on HTTPS transfers - an unresolved timeout issue with streaming of large files - does not support typical apache configs like virtual hosts, hosts allow, hosts deny
Timewise the bottle neck is normally not the database not the web server. In particular sqlite is not a client-server database and only one thread can open it at the time. It also depends on how heavy are you models and actions. On a 2GHz PC and a typical web2py app (with db, sessions, auth, etc.) you are looking at about 100 requests/second. Using apache would make a more solid configuration but it is not change the speed. Massimo On Sep 9, 1:58 am, Arvind <[email protected]> wrote: > Hello, > > This might have been an already asked question. I did not find > anything (maybe i am blind), on google search. > > the default app server that we run as > [/var/web2py]# python web2py.py > > How much load can this handle ? Is it good to run on production > servers with high traffic volume, say, something like a yahoo mail > server ? Can this basic server handle so much load ? > > thanks > Arvind --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
