On Wednesday, July 8, 2015 at 5:53:41 AM UTC-7, Phillip wrote: > > Thank you for the responses. The python code does a lot of processing, so > I need to make sure the application is scalable, and as price-sensitive is > possible >
Some of the contributors here run quite large projects with valuable parts of the processing on the server (a lot of these are database oriented, or handle image processing with database for keeping track of the files). The key to scaling seems to be more in the apache/nginx setup and in using a "grownup" database (sqlite uses large-scale file locking, which can cause one request to delay another), rather than in the Python running under web2py. Where Python performance seems to crop up is if your query returns a large dataset that you then do further processing on by iterating on each row element. On the other hand, some rendering tasks are quite good candidates for client processing, such as spread-sheet like presentation: <URL:http://handsontable.com/> We can't comment intelligently on the performance factors you face without knowing more about what sort of processing you intend to do. /dps -- 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/d/optout.
