On Saturday 22 Aug 2015 17:33 CEST, Michael Torrie wrote: > On 08/22/2015 05:37 AM, Cecil Westerhof wrote: >>> I don't know. Is it bottle, or the browser, or something >>> completely different that eats the extra time? >> >> I really do not know. I suspect bottle, but I am new to this, so I >> value the suspicion of someone who has more experience more. :-D > > These are requests performed from browser Javascript (ajax), right? > Could you write a shell script that fetches these urls in sequence > using curl or wget, simulating the web browser? This would let you > check times in a controlled way, without the variable of the browser > itself.
I should have thought about that myself. :-( I was already thinking about writing debug statements in the routes. By the way does anybody know what the time-stamp is: the moment the requests is received, or the moment the request is finished? I just tried it again. Two almost immediately and then a long one again. What I find very peculiarly is that every-time there is a delay, there are two delays of six seconds. > While it's true this particular problem is possibly beyond the scope > of this python list (and may not be python-related at all), it's too > bad a couple of people have taken the time to reply to your queries > to simply berate you. It could be an AngularJS problem. ;-) -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof -- https://mail.python.org/mailman/listinfo/python-list
