It seems that you are right, I set up a virtual machine with 4gb ram only for the database and I ran the code along with redis on my laptop with 16gb ram and my times now are nearly the 600ms. I think it is good enough. Having some components that don't perform selects rendering only a simple html taking nearly 500ms is suspicious though.
Thank you Leonel! Using redis and assigning more RAM seems to be the best tips to improve the request performance (besides the book recommendations like lazy_tables, pool_size, extraction functions to modules, etc) Just for curiosity, what are the hardware specs of your server? Thank you El viernes, 21 de julio de 2017, 6:19:48 (UTC-5), Leonel Câmara escribió: > > Yes I'm pretty sure it's a RAM issue, 48 free MB is way too low. You > easily start having to use virtual memory with a couple of requests. > > To give you an idea, on a similar setup but a much better machine, I have > a much much more complex page than yours appears to be, with quite a lot of > ajax calls and complex db queries loading everything in 700ms. > -- 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.
