I'm not seeing the slowness. I checked, and maximum time was maybe half a second. Geographically where are you located?
On Monday, March 23, 2015 at 7:53:08 PM UTC-7, NeoToren wrote: > > > 1. > > I have installed the EXACT configuration Web2Py app on MySQL DB with a > different email on your machines. Performance still is unacceptable - but > it is twice as better than the one on the original ICD10 installation ! I > am talking about AVERAGE of 4-6 seconds on the new installation vs. > average > of 15 -30 seconds on the original (I've checked tens of same queries on > both). > 2. > > I've run several queries DIRECTLY on the MySQL instance on your side. > Consistently 0.04-0.08 sec. Very reasonable I'd say. Again - locally on my > Mac - ANY query on this configuration - is sub second. I think we can > safely say the problem is NOT in my SQL code. > 3. > > The above plus the fluctuations in performance during the time of day > - means that Massimo was probably right - the bottle neck is somewhere > between the MySQL and the Web2Py servers. *BTW - what is the webserver > you guys use - Rocket or something else ?* > 4. > > Now to your question, specifically. As you can check yourself at > icd10doc.com: user enters either free text or a specific code in to a > search box. Problem of latency is most annoying with free text where it > may > take 15-60 seconds (?!?) for response. With that being said - even 2-3 > seconds response time on a search with a code (not free text) for a > disease > on an indexed table, when directly on MySQL it is measured in milliseconds > and locally is always sub second - still shows there is a problem. The > MySQL response to the query is just being parsed by Web2Py into a view, > usually with links to other pages. > 5. > > And here is another issue - when user clicks on one link on page - > even though it is a simple query (on an indexed table) which responds with > another W2P view- it still may take 2-5 seconds ! Why ? > > Please - HELP ! > > > Can you tell us a bit more about what kind of query you're running? What's > the direct SQL? And what kind of processing do you do in Python? > [image: Staff] harry | 1156 posts | PythonAnywhere staff | March 23, > 2015, 12:35 p.m. > > > On Saturday, March 21, 2015 at 4:21:40 PM UTC-4, NeoToren wrote: >> >> My website is using MySQL and consists mostly of queries and simple >> display of textual results. No images or fancy CSS. >> >> Locally, queries response time is *sub second*. >> Deployed to PythonAnywhere (using the couple of basic efficiency tricks >> in the book) - and the same queries may take *7-8 seconds each !* >> PA support mentioned that inefficiencies in my code, which are not >> evident locally may become an issue on the network. >> Ok...what kind of inefficiencies should I look for ? >> >> Any ideas how I can improve the performance when hosted at PythonAnywhere >> ? >> Anybody experienced similar issues ? >> >> Thanks >> >> -- 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.