Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #95534 > unrolled thread

Sometimes bottle takes a lot of time

Back to article view | Back to comp.lang.python

Contents

  Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-21 23:22 +0200
    Sometimes bottle takes a lot of time gst <g.starck@gmail.com> - 2015-08-21 14:55 -0700
      Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 13:34 +0200
    Re: Sometimes bottle takes a lot of time Peter Otten <__peter__@web.de> - 2015-08-22 09:49 +0200
      Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 13:37 +0200
        Re: Sometimes bottle takes a lot of time Michael Torrie <torriem@gmail.com> - 2015-08-22 09:33 -0600
          Re: Sometimes bottle takes a lot of time Rustom Mody <rustompmody@gmail.com> - 2015-08-22 09:13 -0700
          Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 20:03 +0200
            Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 23:06 +0200
              Re: Sometimes bottle takes a lot of time Chris Angelico <rosuav@gmail.com> - 2015-08-23 09:13 +1000
                Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-23 02:51 +0200
                  Re: Sometimes bottle takes a lot of time Chris Angelico <rosuav@gmail.com> - 2015-08-23 11:05 +1000
                    Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-23 14:45 +0200
    Re: Sometimes bottle takes a lot of time Johannes Bauer <dfnsonfsduifb@gmx.de> - 2015-08-22 11:41 +0200
      Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 13:28 +0200
        Re: Sometimes bottle takes a lot of time Johannes Bauer <dfnsonfsduifb@gmx.de> - 2015-08-22 14:09 +0200
          Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-22 15:09 +0200
            Re: Sometimes bottle takes a lot of time Johannes Bauer <dfnsonfsduifb@gmx.de> - 2015-08-22 15:51 +0200
              Re: Sometimes bottle takes a lot of time Christian Gollwitzer <auriocus@gmx.de> - 2015-08-22 16:15 +0200
                Re: Sometimes bottle takes a lot of time Johannes Bauer <dfnsonfsduifb@gmx.de> - 2015-08-23 16:05 +0200
                  Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-23 17:20 +0200
                    Re: Sometimes bottle takes a lot of time MRAB <python@mrabarnett.plus.com> - 2015-08-23 16:44 +0100
                      Re: Sometimes bottle takes a lot of time Cecil Westerhof <Cecil@decebal.nl> - 2015-08-23 18:15 +0200
                  Re: Sometimes bottle takes a lot of time Michael Torrie <torriem@gmail.com> - 2015-08-23 10:47 -0600
                    Re: Sometimes bottle takes a lot of time Johannes Bauer <dfnsonfsduifb@gmx.de> - 2015-08-23 22:55 +0200
                      Re: Sometimes bottle takes a lot of time Ben Finney <ben+python@benfinney.id.au> - 2015-08-24 10:01 +1000

Page 1 of 2  [1] 2  Next page →

#95534 — Sometimes bottle takes a lot of time

I created a simple application with bottle:
    https://github.com/CecilWesterhof/PublishedPhotos

But sometimes it needs a lot of time. For example:
127.0.0.1 - - [21/Aug/2015 23:16:40] "GET / HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:40] "GET /static/css/default.css HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /static/JavaScript/angular.js HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /static/appPublishedPhotos.js HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /links/data HTTP/1.1" 200 2884
127.0.0.1 - - [21/Aug/2015 23:16:52] "GET /versionPython HTTP/1.1" 200 5
127.0.0.1 - - [21/Aug/2015 23:16:52] "GET /versionSQLite HTTP/1.1" 200 5

Between default.css and angular.js there are six seconds. And between
/links/data and /versionPytjon is again six seconds. What is happening
here?

Just before everything was done in a second:
127.0.0.1 - - [21/Aug/2015 23:16:22] "GET / HTTP/1.1" 200 956
127.0.0.1 - - [21/Aug/2015 23:16:22] "GET /static/css/default.css HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:22] "GET /static/appPublishedPhotos.js HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:22] "GET /static/JavaScript/angular.js HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:23] "GET /versionPython HTTP/1.1" 200 5
127.0.0.1 - - [21/Aug/2015 23:16:23] "GET /links/data HTTP/1.1" 200 2884
127.0.0.1 - - [21/Aug/2015 23:16:23] "GET /versionSQLite HTTP/1.1" 200 5

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [next] | [standalone]

#95536

What if you try with all the SQLite code commented ?

[toc] | [prev] | [next] | [standalone]

#95552

On Friday 21 Aug 2015 23:55 CEST, gst wrote:

> What if you try with all the SQLite code commented ?

I do not think that is the problem. First of all I do not think
receiving 25 records takes 6 seconds.

Secondly the first part is:
127.0.0.1 - - [21/Aug/2015 23:16:40] "GET / HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:40] "GET /static/css/default.css HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /static/JavaScript/angular.js HTTP/1.1" 304 0
127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /static/appPublishedPhotos.js HTTP/1.1" 304 0

There is no SQLite code at all there. Only Not Modified replies.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95547

Cecil Westerhof wrote:

> I created a simple application with bottle:
>     https://github.com/CecilWesterhof/PublishedPhotos
> 
> But sometimes it needs a lot of time. For example:
> 127.0.0.1 - - [21/Aug/2015 23:16:40] "GET / HTTP/1.1" 304 0
> 127.0.0.1 - - [21/Aug/2015 23:16:40] "GET /static/css/default.css
> HTTP/1.1" 304 0 127.0.0.1 - - [21/Aug/2015 23:16:46] "GET
> /static/JavaScript/angular.js HTTP/1.1" 304 0 127.0.0.1 - - [21/Aug/2015
> 23:16:46] "GET /static/appPublishedPhotos.js HTTP/1.1" 304 0 127.0.0.1 - -
> [21/Aug/2015 23:16:46] "GET /links/data HTTP/1.1" 200 2884 127.0.0.1 - -
> [21/Aug/2015 23:16:52] "GET /versionPython HTTP/1.1" 200 5 127.0.0.1 - -
> [21/Aug/2015 23:16:52] "GET /versionSQLite HTTP/1.1" 200 5
> 
> Between default.css and angular.js there are six seconds. And between
> /links/data and /versionPytjon is again six seconds. What is happening
> here?

I don't know. Is it bottle, or the browser, or something completely 
different that eats the extra time?

> Just before everything was done in a second:
> 127.0.0.1 - - [21/Aug/2015 23:16:22] "GET / HTTP/1.1" 200 956
> 127.0.0.1 - - [21/Aug/2015 23:16:22] "GET /static/css/default.css
> HTTP/1.1" 304 0 127.0.0.1 - - [21/Aug/2015 23:16:22] "GET
> /static/appPublishedPhotos.js HTTP/1.1" 304 0 127.0.0.1 - - [21/Aug/2015
> 23:16:22] "GET /static/JavaScript/angular.js HTTP/1.1" 304 0 127.0.0.1 - -
> [21/Aug/2015 23:16:23] "GET /versionPython HTTP/1.1" 200 5 127.0.0.1 - -
> [21/Aug/2015 23:16:23] "GET /links/data HTTP/1.1" 200 2884 127.0.0.1 - -
> [21/Aug/2015 23:16:23] "GET /versionSQLite HTTP/1.1" 200 5
> 

[toc] | [prev] | [next] | [standalone]

#95551

On Saturday 22 Aug 2015 09:49 CEST, Peter Otten wrote:

> Cecil Westerhof wrote:
>
>> I created a simple application with bottle:
>> https://github.com/CecilWesterhof/PublishedPhotos
>>
>> But sometimes it needs a lot of time. For example: 127.0.0.1 - -
>> [21/Aug/2015 23:16:40] "GET / HTTP/1.1" 304 0 127.0.0.1 - -
>> [21/Aug/2015 23:16:40] "GET /static/css/default.css HTTP/1.1" 304 0
>> 127.0.0.1 - - [21/Aug/2015 23:16:46] "GET
>> /static/JavaScript/angular.js HTTP/1.1" 304 0 127.0.0.1 - -
>> [21/Aug/2015 23:16:46] "GET /static/appPublishedPhotos.js HTTP/1.1"
>> 304 0 127.0.0.1 - - [21/Aug/2015 23:16:46] "GET /links/data
>> HTTP/1.1" 200 2884 127.0.0.1 - - [21/Aug/2015 23:16:52] "GET
>> /versionPython HTTP/1.1" 200 5 127.0.0.1 - - [21/Aug/2015 23:16:52]
>> "GET /versionSQLite HTTP/1.1" 200 5
>>
>> Between default.css and angular.js there are six seconds. And
>> between /links/data and /versionPytjon is again six seconds. What
>> is happening here?
>
> 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


>> Just before everything was done in a second: 127.0.0.1 - -
>> [21/Aug/2015 23:16:22] "GET / HTTP/1.1" 200 956 127.0.0.1 - -
>> [21/Aug/2015 23:16:22] "GET /static/css/default.css HTTP/1.1" 304 0
>> 127.0.0.1 - - [21/Aug/2015 23:16:22] "GET
>> /static/appPublishedPhotos.js HTTP/1.1" 304 0 127.0.0.1 - -
>> [21/Aug/2015 23:16:22] "GET /static/JavaScript/angular.js HTTP/1.1"
>> 304 0 127.0.0.1 - - [21/Aug/2015 23:16:23] "GET /versionPython
>> HTTP/1.1" 200 5 127.0.0.1 - - [21/Aug/2015 23:16:23] "GET
>> /links/data HTTP/1.1" 200 2884 127.0.0.1 - - [21/Aug/2015 23:16:23]
>> "GET /versionSQLite HTTP/1.1" 200 5
>>

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95561

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.

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.

[toc] | [prev] | [next] | [standalone]

#95562

On Saturday, August 22, 2015 at 9:03:52 PM UTC+5:30, Michael Torrie wrote:

> 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.

Yeah -- quite uncalled for.

As for beyond scope, I believe Peter Otten recommended bottle just a
few days ago. So I dont see whats improper about the question.
At some point of course someone may say: "Bottle written in python doesn't 
mean this is a python question."
If after that the questions continue and they are persistent and asinine and...
then berating may be ok. Dont see that here

[toc] | [prev] | [next] | [standalone]

#95564

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

[toc] | [prev] | [next] | [standalone]

#95566

[Multipart message — attachments visible in raw view] — view raw

On Saturday 22 Aug 2015 20:03 CEST, Cecil Westerhof wrote:

> 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 used Python instead of a shell script of-course. :-P

========================================================================
#!/usr/bin/env python3

import time

from urllib.request import urlopen


server = 'http://localhost:8080'
urls   = [
    '/',
    '/static/css/default.css',
    '/static/JavaScript/angular.js',
    '/static/appPublishedPhotos.js',
    '/links/data',
    '/versionPython',
    '/versionSQLite',
]
for x in range(0, 10):
    start_time = time.time()
    for url in urls:
        print(url)
        urlopen(server + url).read()
    end_time = time.time()
    print('It took {0} seconds\n'.format(end_time - start_time), flush = True)
    time.sleep(20)
========================================================================

It is not perfect code, no error checking and the last sleep is
superfluous, but for the current job good enough.

I have included the output as attachment. It is clear that bottle is
not the problem: fetching all the data takes at most 0.017 seconds.

[toc] | [prev] | [next] | [standalone]

#95568

On Sun, Aug 23, 2015 at 7:06 AM, Cecil Westerhof <Cecil@decebal.nl> wrote:
> I have included the output as attachment. It is clear that bottle is
> not the problem: fetching all the data takes at most 0.017 seconds.
>

Something to consider: You could be running into some weird
interaction of caches. Try blowing your OS and browser caches, and see
what the timings are like then. Also, if you can recreate the
six-second delay, I'd want to know what's happening during that time -
is there an open socket between the browser and the server? Is
anything pegging the CPU? Is the disk heavily active? Finding any sort
of saturation would help to pin down the cause of the delay. Do you
have any network mounts in your file system, and could they be
delaying some stat() call somewhere? Six seconds is a lot, but I do
recall running into problems occasionally when I had a NETBIOS/NETBEUI
mount on one of my boxes (Linux couldn't safely cache stuff, and the
remote system was misconfigured as regards caching, I think - the
upshot was terrible performance in certain situations, all of it spent
waiting on the network).

ChrisA

[toc] | [prev] | [next] | [standalone]

#95573

On Sunday 23 Aug 2015 01:13 CEST, Chris Angelico wrote:

> On Sun, Aug 23, 2015 at 7:06 AM, Cecil Westerhof <Cecil@decebal.nl> wrote:
>> I have included the output as attachment. It is clear that bottle
>> is not the problem: fetching all the data takes at most 0.017
>> seconds.
>>
>
> Something to consider: You could be running into some weird
> interaction of caches. Try blowing your OS and browser caches, and
> see what the timings are like then. Also, if you can recreate the
> six-second delay, I'd want to know what's happening during that time
> - is there an open socket between the browser and the server? Is
> anything pegging the CPU? Is the disk heavily active? Finding any
> sort of saturation would help to pin down the cause of the delay. Do
> you have any network mounts in your file system, and could they be
> delaying some stat() call somewhere? Six seconds is a lot, but I do
> recall running into problems occasionally when I had a
> NETBIOS/NETBEUI mount on one of my boxes (Linux couldn't safely
> cache stuff, and the remote system was misconfigured as regards
> caching, I think - the upshot was terrible performance in certain
> situations, all of it spent waiting on the network).

How do I see if there is an open socket?

But in principal I have found the problem. (Not the reason.) The
problem is Firefox. (So it is not bottle and also not AngularJS.) When
using Chrome there is no problem. Not even when I do 15 times a
refresh. With Firefox there is this problem. Even when I restart it.

So I have found the problem and it is certainly not a Python problem.
I should post it on the Firefox, but if there will be an use-full
reply … I have been reading it for a long time. And when someone
mentioned that Firefox used to much CPU or memory the replies where in
my opinion not very helpful.

It even happens with Firefox in safe-mode. Less often and not two
times, but max one time.

Well, first some sleep and then trying to get something useful from
the Firefox mailing-list. ;-)

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95574

On Sun, Aug 23, 2015 at 10:51 AM, Cecil Westerhof <Cecil@decebal.nl> wrote:
> How do I see if there is an open socket?

Depends on your OS. On Linux, I can poke around in /proc or with
commands like netstat and/or lsof. It may be easier to separate client
and server across two computers, which would force the socket to be a
"real" network connection, rather than being optimized away.

> But in principal I have found the problem. (Not the reason.) The
> problem is Firefox. (So it is not bottle and also not AngularJS.) When
> using Chrome there is no problem. Not even when I do 15 times a
> refresh. With Firefox there is this problem. Even when I restart it.

Huh, interesting. I can't help there, but I wish you the very best of
luck in finding it.

ChrisA

[toc] | [prev] | [next] | [standalone]

#95588

On Sunday 23 Aug 2015 03:05 CEST, Chris Angelico wrote:

>> But in principal I have found the problem. (Not the reason.) The
>> problem is Firefox. (So it is not bottle and also not AngularJS.)
>> When using Chrome there is no problem. Not even when I do 15 times
>> a refresh. With Firefox there is this problem. Even when I restart
>> it.
>
> Huh, interesting. I can't help there, but I wish you the very best
> of luck in finding it.

It looks like it is a recent problem. I also installed it on an old
AcerAspire One. The fetch takes there five times as long, but fetching
through Firefox is a lot faster. Not as fast as Chromium, but the
difference is a lot less. But there Ice-wasel 38.0 is used instead of
Firefox 40.

Mozilla wants a life version. I am trying to install it on
PythonAnywhere.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95549

On 21.08.2015 23:22, Cecil Westerhof wrote:

> Just before everything was done in a second:

Since you're on GitHub, why don't you git bisect and find out where you
screwed up instead of trying to get people to remotely debug and profile
your broken code?

Cheers,
Johannes

-- 
>> Wo hattest Du das Beben nochmal GENAU vorhergesagt?
> Zumindest nicht öffentlich!
Ah, der neueste und bis heute genialste Streich unsere großen
Kosmologen: Die Geheim-Vorhersage.
 - Karl Kaos über Rüdiger Thomas in dsa <hidbv3$om2$1@speranza.aioe.org>

[toc] | [prev] | [next] | [standalone]

#95553

On Saturday 22 Aug 2015 11:41 CEST, Johannes Bauer wrote:

> On 21.08.2015 23:22, Cecil Westerhof wrote:
>
>> Just before everything was done in a second:
>
> Since you're on GitHub, why don't you git bisect and find out where
> you screwed up instead of trying to get people to remotely debug and
> profile your broken code?

Are you beaten up by your wife that you need to be this harsh?

If you would have taken a little more time you would have seen that
there where 20 seconds between both logs. I am fast, but not that
fast. It is exactly the same code. I suppose it has to do something
with bottle. Something I use since yesterday. Is it that strange to
look if someone else has had the same problem and maybe a solution?

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95556

On 22.08.2015 13:28, Cecil Westerhof wrote:

> If you would have taken a little more time you would have seen that
> there where 20 seconds between both logs. I am fast, but not that
> fast. It is exactly the same code. I suppose it has to do something
> with bottle. Something I use since yesterday. Is it that strange to
> look if someone else has had the same problem and maybe a solution?

So let me get your story straight:

You're new to bottle and, apparently, web-programming in Python as well.
You're new to sqlite.
You've built some web application using both.
Yesterday it worked perfectly.
Today it doesn't.
Obviously, you suspect bottle is at fault.

Being the very wise Senior Software Engineer that you are, do you really
think that mature software, programmed by people who actually know what
they're doing is at fault? Or do you rather think it maybe could be the
piece-of-junk demo application written by someone who has proven his
utter incompetence comprehensively time and time again?

Since you're the very wise Senior Software Engineer here, why don't you
use an approach that every schoolkid learns in a programming class?
Namely, circle the error, reproduce it reliably. Change your machine,
network setup and change between your software versions. Create a
minimal example that demonstrate the issue. Then, should you find one,
blame bottle. Not sooner, very wise Senior Software Engineer, not sooner.

Cheers,
Johannes

-- 
>> Wo hattest Du das Beben nochmal GENAU vorhergesagt?
> Zumindest nicht öffentlich!
Ah, der neueste und bis heute genialste Streich unsere großen
Kosmologen: Die Geheim-Vorhersage.
 - Karl Kaos über Rüdiger Thomas in dsa <hidbv3$om2$1@speranza.aioe.org>

[toc] | [prev] | [next] | [standalone]

#95558

On Saturday 22 Aug 2015 14:09 CEST, Johannes Bauer wrote:

> On 22.08.2015 13:28, Cecil Westerhof wrote:
>
>> If you would have taken a little more time you would have seen that
>> there where 20 seconds between both logs. I am fast, but not that
>> fast. It is exactly the same code. I suppose it has to do something
>> with bottle. Something I use since yesterday. Is it that strange to
>> look if someone else has had the same problem and maybe a solution?
>
> So let me get your story straight:

I wish you really meant that. You just like to bash people. I am
afraid I need to ignore you.

Have a happy life. Do not forget to look in the mirror. Will be
painful in the short term, but very beneficial in the long term.

Also: take a course in reading.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

#95559

On 22.08.2015 15:09, Cecil Westerhof wrote:

>> So let me get your story straight:
> 
> I wish you really meant that.

I really do, did I get it wrong at all? I really don't think that I did.

> Also: take a course in reading.

Maybe you, oh very wise Senior Software Engineer, should take a course
in Software Engineering. You wouldn't otherwise ask embarassingly stupid
questions over and over and over again. Really eats away at your
seniority if you ask me.

Cheers,
Johannes

-- 
>> Wo hattest Du das Beben nochmal GENAU vorhergesagt?
> Zumindest nicht öffentlich!
Ah, der neueste und bis heute genialste Streich unsere großen
Kosmologen: Die Geheim-Vorhersage.
 - Karl Kaos über Rüdiger Thomas in dsa <hidbv3$om2$1@speranza.aioe.org>

[toc] | [prev] | [next] | [standalone]

#95560

Am 22.08.15 um 15:51 schrieb Johannes Bauer:
> On 22.08.2015 15:09, Cecil Westerhof wrote:
>
>>> So let me get your story straight:
>>
>> I wish you really meant that.
>
> I really do, did I get it wrong at all? I really don't think that I did.

Probably yes. You should take a look at the OP again and compare the 
time stamps. It says that in between two consecutive calls of the same 
program, the request was served once in a second, and once with serious 
delays. Despite that the server is localhost. In between both trials 
there are 20 seconds. I do not see, how git bisect would help here.

Note that this says nothing about the location of the bug, in can still 
be either in the OPs code or in the framework.

	Christian

[toc] | [prev] | [next] | [standalone]

#95591

On 22.08.2015 16:15, Christian Gollwitzer wrote:

> Probably yes. You should take a look at the OP again and compare the
> time stamps. It says that in between two consecutive calls of the same
> program, the request was served once in a second, and once with serious
> delays. Despite that the server is localhost. In between both trials
> there are 20 seconds. I do not see, how git bisect would help here.

I do completely understand that in two consecutive runs one time the
problem occurs and the other time it doesn't.

It's highly unlikely that such a bug would ever have passed the bottle
QA and if it did it would affect thousands of users (who would report
this issue, since it's very severe). It is much more likely the bug is
somewhere within the OP's program. By git bisect he can find out where
he introduced the bug.

> Note that this says nothing about the location of the bug, in can still
> be either in the OPs code or in the framework.

Yup. Note that he has now shifted from blaming bottle to blaming
Firefox. Same thing with that claim. If somehow website delivery was
delayed 6 seconds reproducibly, people would have noticed.

I suspect that either the OPs program is at fault or the OP's setup
(name resolution or some other weird stuff going on). But instead of
tackling this problem systematically, like a Software Engineer would
(Wireshark, debugger, profiler) he just blames other people's software.
This, in my humble opinion, is annoying as fuck.

Cheers,
Johannes

-- 
>> Wo hattest Du das Beben nochmal GENAU vorhergesagt?
> Zumindest nicht öffentlich!
Ah, der neueste und bis heute genialste Streich unsere großen
Kosmologen: Die Geheim-Vorhersage.
 - Karl Kaos über Rüdiger Thomas in dsa <hidbv3$om2$1@speranza.aioe.org>

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.python

csiph-web