[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[mdipierro]

I will wait for the patch from you or Jonathan. I can wait the week-
end.

On Dec 1, 8:39 am, Timbo  wrote:
> Rocket 1.2.0 is out.  It addresses the issue above and has some speed
> improvements (though that might not be noticeable to the user).  If
> you look at the code, it's much cleaner than it was and reflects my
> maturing skill as a developer.  I've tested it on cPython 2.4 (the
> legacy branch support Py2.4), 2.5, 2.6, 3.1, Jython 2.5.1 and Pypy 1.4
> on Windows 7 and cPython 2.6 on Ubuntu.
>
> While building a patch for web2py is not that complicated, I'm time-
> restricted until the weekend.  If you can't wait that long, bug
> Jonathan Lundell.  He's familiar enough to do it.  ;-)
>
> Cheers,
> -tim
>
> On Nov 24, 10:37 am, Timbo  wrote:
>
> > I didn't mean to imply that the enhancements I'm planning for 1.2
> > (window speed) address this issue...just to be clear.
>
> > @Jonathan: Yes we need to make numthreads map to max-threads and
> > default it to 0 (unlimited) or a very high number.  The only time
> > reasonable to change this is when running web2py (rocket) on Jython.
> > See:
>
> >http://packages.python.org/rocket/usage.html#architecture-considerations
>
> > @Phyo: Thanks.  I'm not fully recovered, but enough to get back in the
> > game.
>
> > -tim
>
> > On Nov 24, 9:56 am, Jonathan Lundell  wrote:
>
> > > On Nov 24, 2010, at 5:59 AM, Phyo Arkar wrote:
>
> > > > I haven't tried DEFAULT_MAX_THREADS it yet but to report that it is not 
> > > > just windows problem it happens in Linux too.
> > > > WHen i test my Homepage which dont do anything dynamic much , just 
> > > > login box , with static js and css. That caused long load delays too.
>
> > > By all means give max-threads a try. If the problem is thread starvation, 
> > > it's not likely to be Windows-specific. The default limit is 10, which 
> > > isn't a lot for pages with a lot of resources.
>
> > > > Tim , sorry to know that u got injury. Had you recovered well now?
>
> > > > On Wed, Nov 24, 2010 at 12:01 PM, Jonathan Lundell  
> > > > wrote:
> > > > On Nov 23, 2010, at 8:48 PM, Anthony wrote:
>
> > > > > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> > > > >>> On Nov 23, 8:10 pm, Timbo  wrote:
> > > >  Set numthreads=0 in your options.py.  See if you still see this
> > > >  behavior.
>
> > > > >>> options.py is just for running web2py as a Windows service, no? I'm
> > > > >>> not running web2py as a Windows service when I observe the problem.
>
> > > > >> If you're running from the command line, use --options 0.
>
> > > > > Do you mean use the -n command line option to set numthreads to 0,
> > > > > e.g.:
>
> > > > >   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
>
> > > > > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > > > > all (it just hangs indefinitely).
>
> > > > Right, now that I look at it, there's no way to override max_threads. 
> > > > Maybe there should be
>
>

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Timbo]

Rocket 1.2.0 is out.  It addresses the issue above and has some speed
improvements (though that might not be noticeable to the user).  If
you look at the code, it's much cleaner than it was and reflects my
maturing skill as a developer.  I've tested it on cPython 2.4 (the
legacy branch support Py2.4), 2.5, 2.6, 3.1, Jython 2.5.1 and Pypy 1.4
on Windows 7 and cPython 2.6 on Ubuntu.

While building a patch for web2py is not that complicated, I'm time-
restricted until the weekend.  If you can't wait that long, bug
Jonathan Lundell.  He's familiar enough to do it.  ;-)

Cheers,
-tim

On Nov 24, 10:37 am, Timbo  wrote:
> I didn't mean to imply that the enhancements I'm planning for 1.2
> (window speed) address this issue...just to be clear.
>
> @Jonathan: Yes we need to make numthreads map to max-threads and
> default it to 0 (unlimited) or a very high number.  The only time
> reasonable to change this is when running web2py (rocket) on Jython.
> See:
>
> http://packages.python.org/rocket/usage.html#architecture-considerations
>
> @Phyo: Thanks.  I'm not fully recovered, but enough to get back in the
> game.
>
> -tim
>
> On Nov 24, 9:56 am, Jonathan Lundell  wrote:
>
>
>
>
>
>
>
> > On Nov 24, 2010, at 5:59 AM, Phyo Arkar wrote:
>
> > > I haven't tried DEFAULT_MAX_THREADS it yet but to report that it is not 
> > > just windows problem it happens in Linux too.
> > > WHen i test my Homepage which dont do anything dynamic much , just login 
> > > box , with static js and css. That caused long load delays too.
>
> > By all means give max-threads a try. If the problem is thread starvation, 
> > it's not likely to be Windows-specific. The default limit is 10, which 
> > isn't a lot for pages with a lot of resources.
>
> > > Tim , sorry to know that u got injury. Had you recovered well now?
>
> > > On Wed, Nov 24, 2010 at 12:01 PM, Jonathan Lundell  
> > > wrote:
> > > On Nov 23, 2010, at 8:48 PM, Anthony wrote:
>
> > > > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> > > >>> On Nov 23, 8:10 pm, Timbo  wrote:
> > >  Set numthreads=0 in your options.py.  See if you still see this
> > >  behavior.
>
> > > >>> options.py is just for running web2py as a Windows service, no? I'm
> > > >>> not running web2py as a Windows service when I observe the problem.
>
> > > >> If you're running from the command line, use --options 0.
>
> > > > Do you mean use the -n command line option to set numthreads to 0,
> > > > e.g.:
>
> > > >   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
>
> > > > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > > > all (it just hangs indefinitely).
>
> > > Right, now that I look at it, there's no way to override max_threads. 
> > > Maybe there should be

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Timbo]

I didn't mean to imply that the enhancements I'm planning for 1.2
(window speed) address this issue...just to be clear.

@Jonathan: Yes we need to make numthreads map to max-threads and
default it to 0 (unlimited) or a very high number.  The only time
reasonable to change this is when running web2py (rocket) on Jython.
See:

http://packages.python.org/rocket/usage.html#architecture-considerations

@Phyo: Thanks.  I'm not fully recovered, but enough to get back in the
game.

-tim

On Nov 24, 9:56 am, Jonathan Lundell  wrote:
> On Nov 24, 2010, at 5:59 AM, Phyo Arkar wrote:
>
> > I haven't tried DEFAULT_MAX_THREADS it yet but to report that it is not 
> > just windows problem it happens in Linux too.
> > WHen i test my Homepage which dont do anything dynamic much , just login 
> > box , with static js and css. That caused long load delays too.
>
> By all means give max-threads a try. If the problem is thread starvation, 
> it's not likely to be Windows-specific. The default limit is 10, which isn't 
> a lot for pages with a lot of resources.
>
>
>
>
>
>
>
>
>
> > Tim , sorry to know that u got injury. Had you recovered well now?
>
> > On Wed, Nov 24, 2010 at 12:01 PM, Jonathan Lundell  
> > wrote:
> > On Nov 23, 2010, at 8:48 PM, Anthony wrote:
>
> > > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> > >>> On Nov 23, 8:10 pm, Timbo  wrote:
> >  Set numthreads=0 in your options.py.  See if you still see this
> >  behavior.
>
> > >>> options.py is just for running web2py as a Windows service, no? I'm
> > >>> not running web2py as a Windows service when I observe the problem.
>
> > >> If you're running from the command line, use --options 0.
>
> > > Do you mean use the -n command line option to set numthreads to 0,
> > > e.g.:
>
> > >   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
>
> > > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > > all (it just hangs indefinitely).
>
> > Right, now that I look at it, there's no way to override max_threads. Maybe 
> > there should be

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Jonathan Lundell]

On Nov 24, 2010, at 5:59 AM, Phyo Arkar wrote:
> I haven't tried DEFAULT_MAX_THREADS it yet but to report that it is not just 
> windows problem it happens in Linux too.
> WHen i test my Homepage which dont do anything dynamic much , just login box 
> , with static js and css. That caused long load delays too.

By all means give max-threads a try. If the problem is thread starvation, it's 
not likely to be Windows-specific. The default limit is 10, which isn't a lot 
for pages with a lot of resources.

> 
> Tim , sorry to know that u got injury. Had you recovered well now?
> 
> 
> On Wed, Nov 24, 2010 at 12:01 PM, Jonathan Lundell  wrote:
> On Nov 23, 2010, at 8:48 PM, Anthony wrote:
> >
> > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> >>> On Nov 23, 8:10 pm, Timbo  wrote:
>  Set numthreads=0 in your options.py.  See if you still see this
>  behavior.
> >>
> >>> options.py is just for running web2py as a Windows service, no? I'm
> >>> not running web2py as a Windows service when I observe the problem.
> >>
> >> If you're running from the command line, use --options 0.
> >
> > Do you mean use the -n command line option to set numthreads to 0,
> > e.g.:
> >
> >   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
> >
> > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > all (it just hangs indefinitely).
> 
> Right, now that I look at it, there's no way to override max_threads. Maybe 
> there should be
> 

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

I haven't tried DEFAULT_MAX_THREADS it yet but to report that it is not just
windows problem it happens in Linux too.
WHen i test my Homepage which dont do anything dynamic much , just login box
, with static js and css. That caused long load delays too.

Tim , sorry to know that u got injury. Had you recovered well now?


On Wed, Nov 24, 2010 at 12:01 PM, Jonathan Lundell wrote:

> On Nov 23, 2010, at 8:48 PM, Anthony wrote:
> >
> > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> >>> On Nov 23, 8:10 pm, Timbo  wrote:
>  Set numthreads=0 in your options.py.  See if you still see this
>  behavior.
> >>
> >>> options.py is just for running web2py as a Windows service, no? I'm
> >>> not running web2py as a Windows service when I observe the problem.
> >>
> >> If you're running from the command line, use --options 0.
> >
> > Do you mean use the -n command line option to set numthreads to 0,
> > e.g.:
> >
> >   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
> >
> > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > all (it just hangs indefinitely).
>
> Right, now that I look at it, there's no way to override max_threads. Maybe
> there should be

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Jonathan Lundell]

On Nov 23, 2010, at 8:48 PM, Anthony wrote:
> 
> On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
>>> On Nov 23, 8:10 pm, Timbo  wrote:
 Set numthreads=0 in your options.py.  See if you still see this
 behavior.
>> 
>>> options.py is just for running web2py as a Windows service, no? I'm
>>> not running web2py as a Windows service when I observe the problem.
>> 
>> If you're running from the command line, use --options 0.
> 
> Do you mean use the -n command line option to set numthreads to 0,
> e.g.:
> 
>   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
> 
> I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> all (it just hangs indefinitely).

Right, now that I look at it, there's no way to override max_threads. Maybe 
there should be

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Timbo]

That's essentially the effect I was going for.  No need to change
DEFAULT_MIN_THREADS, changing DEFAULT_MAX_THREADS should have the
desired effect.

On Nov 23, 10:59 pm, Anthony  wrote:
> I went into rocket.py and set both DEFAULT_MIN_THREADS and
> DEFAULT_MAX_THREADS to 0, and the problem I described (i.e., long load
> times when trying to load apps into separate IE browser tabs) seems to
> go away (apps now load instantly in new IE tabs).
>
> Anthony
>
> On Nov 23, 11:48 pm, Anthony  wrote:
>
>
>
>
>
>
>
> > On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
>
> > > > On Nov 23, 8:10 pm, Timbo  wrote:
> > > >> Set numthreads=0 in your options.py.  See if you still see this
> > > >> behavior.
>
> > > > options.py is just for running web2py as a Windows service, no? I'm
> > > > not running web2py as a Windows service when I observe the problem.
>
> > > If you're running from the command line, use --options 0.
>
> > Do you mean use the -n command line option to set numthreads to 0,
> > e.g.:
>
> >    python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
>
> > I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> > all (it just hangs indefinitely).
>
> > Anthony

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

I went into rocket.py and set both DEFAULT_MIN_THREADS and
DEFAULT_MAX_THREADS to 0, and the problem I described (i.e., long load
times when trying to load apps into separate IE browser tabs) seems to
go away (apps now load instantly in new IE tabs).

Anthony

On Nov 23, 11:48 pm, Anthony  wrote:
> On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
>
> > > On Nov 23, 8:10 pm, Timbo  wrote:
> > >> Set numthreads=0 in your options.py.  See if you still see this
> > >> behavior.
>
> > > options.py is just for running web2py as a Windows service, no? I'm
> > > not running web2py as a Windows service when I observe the problem.
>
> > If you're running from the command line, use --options 0.
>
> Do you mean use the -n command line option to set numthreads to 0,
> e.g.:
>
>    python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0
>
> I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
> all (it just hangs indefinitely).
>
> Anthony

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

On Nov 23, 9:26 pm, Jonathan Lundell  wrote:
> > On Nov 23, 8:10 pm, Timbo  wrote:
> >> Set numthreads=0 in your options.py.  See if you still see this
> >> behavior.
>
> > options.py is just for running web2py as a Windows service, no? I'm
> > not running web2py as a Windows service when I observe the problem.
>
> If you're running from the command line, use --options 0.

Do you mean use the -n command line option to set numthreads to 0,
e.g.:

   python web2py.py -a password -i 127.0.0.1 -p 8000 -n 0

I tried this, but in that case, I can't get 127.0.0.1:8000 to load at
all (it just hangs indefinitely).

Anthony

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Jonathan Lundell]

On Nov 23, 2010, at 5:26 PM, Anthony wrote:
> 
> On Nov 23, 8:10 pm, Timbo  wrote:
>> Set numthreads=0 in your options.py.  See if you still see this
>> behavior.
> 
> options.py is just for running web2py as a Windows service, no? I'm
> not running web2py as a Windows service when I observe the problem.

If you're running from the command line, use --options 0.

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

On Nov 23, 8:10 pm, Timbo  wrote:
> Set numthreads=0 in your options.py.  See if you still see this
> behavior.

options.py is just for running web2py as a Windows service, no? I'm
not running web2py as a Windows service when I observe the problem.

Anthony

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Timbo]

Set numthreads=0 in your options.py.  See if you still see this
behavior.

-tim

On Nov 23, 7:03 pm, Timbo  wrote:
> Rocket is not dead but I did take several months off due to injury and
> a job change.  I'm actually working on 1.2 which should see some
> performance improvements on Windows.
>
> I'll go download a copy of web2py and report back.
>
> -tim
>
> On Nov 22, 5:25 pm, Phyo Arkar  wrote:
>
>
>
>
>
>
>
> > Hmm rocket server issue again..?
>
> > also what i see is Rocket server is not updated for very long , Massimo , is
> > Rocket still in development or dead ? , i dont see any development updates
> > there..
>
> > On Tue, Nov 23, 2010 at 5:04 AM, Kuba Kucharski 
> > wrote:
>
> > > Just a hyphotesis, I've seen the issue you are describing many times.
> > > It always disapears when I move from Rocket to Apache/WSGI. It seems
> > > to me that it got smth to do with handling static files.
>
> > > --
> > > Kuba

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Timbo]

Rocket is not dead but I did take several months off due to injury and
a job change.  I'm actually working on 1.2 which should see some
performance improvements on Windows.

I'll go download a copy of web2py and report back.

-tim

On Nov 22, 5:25 pm, Phyo Arkar  wrote:
> Hmm rocket server issue again..?
>
> also what i see is Rocket server is not updated for very long , Massimo , is
> Rocket still in development or dead ? , i dont see any development updates
> there..
>
> On Tue, Nov 23, 2010 at 5:04 AM, Kuba Kucharski 
> wrote:
>
>
>
>
>
>
>
> > Just a hyphotesis, I've seen the issue you are describing many times.
> > It always disapears when I move from Rocket to Apache/WSGI. It seems
> > to me that it got smth to do with handling static files.
>
> > --
> > Kuba

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

Hmm rocket server issue again..?

also what i see is Rocket server is not updated for very long , Massimo , is
Rocket still in development or dead ? , i dont see any development updates
there..



On Tue, Nov 23, 2010 at 5:04 AM, Kuba Kucharski wrote:

> Just a hyphotesis, I've seen the issue you are describing many times.
> It always disapears when I move from Rocket to Apache/WSGI. It seems
> to me that it got smth to do with handling static files.
>
> --
> Kuba
>

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

On Nov 22, 5:34 pm, Kuba Kucharski  wrote:
> Just a hyphotesis, I've seen the issue you are describing many times.
> It always disapears when I move from Rocket to Apache/WSGI. It seems
> to me that it got smth to do with handling static files.

You might be onto something. Sometimes once the examples app has
partially loaded, it continues to hang as it tries to load some of the
images from the static folder (at that point, hitting refresh often
quickly resolves the problem).

Anthony

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

It still happening for Anthony and Carlos.

On Tue, Nov 23, 2010 at 5:07 AM, Kuba Kucharski wrote:

> ok, if it disappers on unpluging network, that it is not that issue, sorry
>

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Kuba Kucharski]

ok, if it disappers on unpluging network, that it is not that issue, sorry

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Kuba Kucharski]

Just a hyphotesis, I've seen the issue you are describing many times.
It always disapears when I move from Rocket to Apache/WSGI. It seems
to me that it got smth to do with handling static files.

-- 
Kuba

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

Oh well i tried with ffox and chrome , under linux..

On Mon, Nov 22, 2010 at 10:45 AM, Anthony  wrote:

> On Nov 21, 9:48 pm, Phyo Arkar  wrote:
> > I tested , opened 20 welcome pages atonce , and also my application at
> once.
> > No slow down (not trunk but i commented out google cdn jquerys). So that
> > fixed for me.
>
> Which OS and browser? I'm on Windows 7, and the problem is mostly with
> IE.
>
> Anthony

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

On Nov 21, 9:48 pm, Phyo Arkar  wrote:
> I tested , opened 20 welcome pages atonce , and also my application at once.
> No slow down (not trunk but i commented out google cdn jquerys). So that
> fixed for me.

Which OS and browser? I'm on Windows 7, and the problem is mostly with
IE.

Anthony

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

I tested , opened 20 welcome pages atonce , and also my application at once.
No slow down (not trunk but i commented out google cdn jquerys). So that
fixed for me.

On Mon, Nov 22, 2010 at 4:15 AM, Anthony  wrote:

> Yes, I'm running trunk, which Massimo already updated to run jQuery
> locally.
>
> On Nov 21, 4:16 pm, Phyo Arkar  wrote:
> > Have you guys made jquery load locally instead of google's CDN ?
> >
> > Still happening?
> >
> > For me it fixed after i fixed to load jquery locally.
> >
> > On 11/22/10, Anthony  wrote:
> >
> >
> >
> > > Same thing here (actually, I think it happens even when loading a
> > > different web2py app in another browser).
> >
> > > Anthony
> >
> > > On Nov 21, 2:11 pm, David Marko  wrote:
> > >> ### I have problems when I call the same page with multiple browsers
> > >> at the same time.
> > >> I can see the same problem. I use Chrome as primary browser. Then when
> > >> I try to test the page in other browsers(FF, MSIE etc.) the page load
> > >> time is very, very slow.
> >
> > >> David
> >
> > >> On 21 lis, 20:00, selecta  wrote:
> >
> > >> > I have problems when I call the same page with multiple browsers at
> > >> > the same time. As soon as i close all but one browser the page
> > >> > loads. ... but thinking about it this should be unrelated
> >
> > >> > On Nov 21, 2:50 am, Carlos  wrote:
> >
> > >> > > Hi,
> >
> > >> > > Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> > >> > > often take a LOOONG time to load web2py urls in the following
> format?:
> >
> > >> > >http://127.0.0.1:8000/
> >
> > >> > > I just see in the following in the status bar:
> >
> > >> > >Waiting forhttp://127.0.0.1:8000/...
> >
> > >> > > Even after trying to refresh/reload many times, and then all of
> the
> > >> > > sudden everything work ok, until the delays occur again !
> >
> > >> > > When using Chrome, I never have to wait, there are no delays, and
> > >> > > everything is very fast.
> >
> > >> > > I'm using web2py 1.89.1 source on win7.
> >
> > >> > > Any ideas?.
> >
> > >> > > Thanks,
> >
> > >> > >Carlos- Hide quoted text -
> >
> > >> - Show quoted text -- Hide quoted text -
> >
> > - Show quoted text -

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[David Marko]

### I have problems when I call the same page with multiple browsers
at the same time.
I can see the same problem. I use Chrome as primary browser. Then when
I try to test the page in other browsers(FF, MSIE etc.) the page load
time is very, very slow.

David

On 21 lis, 20:00, selecta  wrote:
> I have problems when I call the same page with multiple browsers at
> the same time. As soon as i close all but one browser the page
> loads. ... but thinking about it this should be unrelated
>
> On Nov 21, 2:50 am, Carlos  wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> > often take a LOOONG time to load web2py urls in the following format?:
>
> >    http://127.0.0.1:8000/
>
> > I just see in the following in the status bar:
>
> >    Waiting forhttp://127.0.0.1:8000/...
>
> > Even after trying to refresh/reload many times, and then all of the
> > sudden everything work ok, until the delays occur again !
>
> > When using Chrome, I never have to wait, there are no delays, and
> > everything is very fast.
>
> > I'm using web2py 1.89.1 source on win7.
>
> > Any ideas?.
>
> > Thanks,
>
> >    Carlos

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

Yes, I'm running trunk, which Massimo already updated to run jQuery
locally.

On Nov 21, 4:16 pm, Phyo Arkar  wrote:
> Have you guys made jquery load locally instead of google's CDN ?
>
> Still happening?
>
> For me it fixed after i fixed to load jquery locally.
>
> On 11/22/10, Anthony  wrote:
>
>
>
> > Same thing here (actually, I think it happens even when loading a
> > different web2py app in another browser).
>
> > Anthony
>
> > On Nov 21, 2:11 pm, David Marko  wrote:
> >> ### I have problems when I call the same page with multiple browsers
> >> at the same time.
> >> I can see the same problem. I use Chrome as primary browser. Then when
> >> I try to test the page in other browsers(FF, MSIE etc.) the page load
> >> time is very, very slow.
>
> >> David
>
> >> On 21 lis, 20:00, selecta  wrote:
>
> >> > I have problems when I call the same page with multiple browsers at
> >> > the same time. As soon as i close all but one browser the page
> >> > loads. ... but thinking about it this should be unrelated
>
> >> > On Nov 21, 2:50 am, Carlos  wrote:
>
> >> > > Hi,
>
> >> > > Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> >> > > often take a LOOONG time to load web2py urls in the following format?:
>
> >> > >    http://127.0.0.1:8000/
>
> >> > > I just see in the following in the status bar:
>
> >> > >    Waiting forhttp://127.0.0.1:8000/...
>
> >> > > Even after trying to refresh/reload many times, and then all of the
> >> > > sudden everything work ok, until the delays occur again !
>
> >> > > When using Chrome, I never have to wait, there are no delays, and
> >> > > everything is very fast.
>
> >> > > I'm using web2py 1.89.1 source on win7.
>
> >> > > Any ideas?.
>
> >> > > Thanks,
>
> >> > >    Carlos- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

Have you guys made jquery load locally instead of google's CDN ?

Still happening?

For me it fixed after i fixed to load jquery locally.

On 11/22/10, Anthony  wrote:
> Same thing here (actually, I think it happens even when loading a
> different web2py app in another browser).
>
> Anthony
>
> On Nov 21, 2:11 pm, David Marko  wrote:
>> ### I have problems when I call the same page with multiple browsers
>> at the same time.
>> I can see the same problem. I use Chrome as primary browser. Then when
>> I try to test the page in other browsers(FF, MSIE etc.) the page load
>> time is very, very slow.
>>
>> David
>>
>> On 21 lis, 20:00, selecta  wrote:
>>
>>
>>
>> > I have problems when I call the same page with multiple browsers at
>> > the same time. As soon as i close all but one browser the page
>> > loads. ... but thinking about it this should be unrelated
>>
>> > On Nov 21, 2:50 am, Carlos  wrote:
>>
>> > > Hi,
>>
>> > > Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
>> > > often take a LOOONG time to load web2py urls in the following format?:
>>
>> > >    http://127.0.0.1:8000/
>>
>> > > I just see in the following in the status bar:
>>
>> > >    Waiting forhttp://127.0.0.1:8000/...
>>
>> > > Even after trying to refresh/reload many times, and then all of the
>> > > sudden everything work ok, until the delays occur again !
>>
>> > > When using Chrome, I never have to wait, there are no delays, and
>> > > everything is very fast.
>>
>> > > I'm using web2py 1.89.1 source on win7.
>>
>> > > Any ideas?.
>>
>> > > Thanks,
>>
>> > >    Carlos- Hide quoted text -
>>
>> - Show quoted text -

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Anthony]

Same thing here (actually, I think it happens even when loading a
different web2py app in another browser).

Anthony

On Nov 21, 2:11 pm, David Marko  wrote:
> ### I have problems when I call the same page with multiple browsers
> at the same time.
> I can see the same problem. I use Chrome as primary browser. Then when
> I try to test the page in other browsers(FF, MSIE etc.) the page load
> time is very, very slow.
>
> David
>
> On 21 lis, 20:00, selecta  wrote:
>
>
>
> > I have problems when I call the same page with multiple browsers at
> > the same time. As soon as i close all but one browser the page
> > loads. ... but thinking about it this should be unrelated
>
> > On Nov 21, 2:50 am, Carlos  wrote:
>
> > > Hi,
>
> > > Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> > > often take a LOOONG time to load web2py urls in the following format?:
>
> > >    http://127.0.0.1:8000/
>
> > > I just see in the following in the status bar:
>
> > >    Waiting forhttp://127.0.0.1:8000/...
>
> > > Even after trying to refresh/reload many times, and then all of the
> > > sudden everything work ok, until the delays occur again !
>
> > > When using Chrome, I never have to wait, there are no delays, and
> > > everything is very fast.
>
> > > I'm using web2py 1.89.1 source on win7.
>
> > > Any ideas?.
>
> > > Thanks,
>
> > >    Carlos- Hide quoted text -
>
> - Show quoted text -

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[selecta]

I have problems when I call the same page with multiple browsers at
the same time. As soon as i close all but one browser the page
loads. ... but thinking about it this should be unrelated

On Nov 21, 2:50 am, Carlos  wrote:
> Hi,
>
> Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> often take a LOOONG time to load web2py urls in the following format?:
>
>    http://127.0.0.1:8000/
>
> I just see in the following in the status bar:
>
>    Waiting forhttp://127.0.0.1:8000/...
>
> Even after trying to refresh/reload many times, and then all of the
> sudden everything work ok, until the delays occur again !
>
> When using Chrome, I never have to wait, there are no delays, and
> everything is very fast.
>
> I'm using web2py 1.89.1 source on win7.
>
> Any ideas?.
>
> Thanks,
>
>    Carlos

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Jason Brower]

Actually, if you just unplug your internet before you start.  It will
just fly because it gets the error and just uses the local one.  But
that's not a solution for everyone.  My network cable is a local network
online and having it plugged in makes the browser look for the page for
about a minute.

On Sun, 2010-11-21 at 09:44 +0630, Phyo Arkar wrote:

> >"Welcome loads Jquery from cdn.google"
> 
> Yea that explain for my case , i have slow internet connection (well
> the whole contry here is slow internet) .
> 
> Thats why it get slow after updated.Carlos loading javascript outside
> of the localhost make it bad response time for app. and it is not ajax
> (not document ready yet) so may be that caused you?
> 
> On 11/21/10, Carlos  wrote:
> > This issue is not related to any extra/ajax loading (e.g. in admin or
> > so), I've tried it with everything: admin, appadmin, welcome, my app,
> > etc., same long delay.
> >
> > The load takes about one full minute !
> >
> > Strangely it only occurs *intermitently* in IE and Firefox, but Chrome
> > (and maybe Opera) work ok all the time.
> >
> > I use AVG free antivirus.
> >
> > Any other info I should provide?, any other ideas?.
> >
> > Thanks,
> >
> >Carlos
> >
> >
> > On Nov 20, 8:33 pm, mdipierro  wrote:
> >> yes. the twitten part is loaded via ajax. Should not cause the delay.
> >>
> >> On Nov 20, 8:10 pm, Phyo Arkar  wrote:
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> > I got very long loading time on examples ., it just waiting for (about
> >> > 10-15 seconds) and do nothing.http://127.0.0.1:8000/examples
> >>
> >> > I suspect Twitter loads but they supposed to be load after document is
> >> > ready, right?
> >>
> >> > On 11/21/10, Bruno Rocha  wrote:
> >>
> >> > > Windows firewall, browser security settings or some antivirus system?
> >>
> >> > > 2010/11/20 Carlos 
> >>
> >> > >> Hi,
> >>
> >> > >> Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> >> > >> often take a LOOONG time to load web2py urls in the following
> >> > >> format?:
> >>
> >> > >>  http://127.0.0.1:8000/
> >>
> >> > >> I just see in the following in the status bar:
> >>
> >> > >>   Waiting forhttp://127.0.0.1:8000/...
> >>
> >> > >> Even after trying to refresh/reload many times, and then all of the
> >> > >> sudden everything work ok, until the delays occur again !
> >>
> >> > >> When using Chrome, I never have to wait, there are no delays, and
> >> > >> everything is very fast.
> >>
> >> > >> I'm using web2py 1.89.1 source on win7.
> >>
> >> > >> Any ideas?.
> >>
> >> > >> Thanks,
> >>
> >> > >>   Carlos
> >>
> >> > > --
> >>
> >> > > Bruno Rocha
> >> > >http://about.me/rochacbruno/bio

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

Massimo , i think web2py local default app should not load code from non-local.
.
In some place where theres no internet everytime (many third world
countries) , it will cause problems .If a new comer tried while
internet is down , that will caused bad impression for web2py

On 11/21/10, Luis Díaz  wrote:
> I had a similar problem and was produced by my work poxy
>
> if you are behind a proxy, I recommend you disable it in your browser while
> you do local tests.
>
> --
> google translator
>
> --
> Díaz Luis
> TSU Analisis de Sistemas
> Universidad de Carabobo
>
> http://web2pyfacil.blogspot.com/
> Facultad de
> Odontología
>

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Phyo Arkar]

>"Welcome loads Jquery from cdn.google"

Yea that explain for my case , i have slow internet connection (well
the whole contry here is slow internet) .

Thats why it get slow after updated.Carlos loading javascript outside
of the localhost make it bad response time for app. and it is not ajax
(not document ready yet) so may be that caused you?

On 11/21/10, Carlos  wrote:
> This issue is not related to any extra/ajax loading (e.g. in admin or
> so), I've tried it with everything: admin, appadmin, welcome, my app,
> etc., same long delay.
>
> The load takes about one full minute !
>
> Strangely it only occurs *intermitently* in IE and Firefox, but Chrome
> (and maybe Opera) work ok all the time.
>
> I use AVG free antivirus.
>
> Any other info I should provide?, any other ideas?.
>
> Thanks,
>
>Carlos
>
>
> On Nov 20, 8:33 pm, mdipierro  wrote:
>> yes. the twitten part is loaded via ajax. Should not cause the delay.
>>
>> On Nov 20, 8:10 pm, Phyo Arkar  wrote:
>>
>>
>>
>>
>>
>>
>>
>> > I got very long loading time on examples ., it just waiting for (about
>> > 10-15 seconds) and do nothing.http://127.0.0.1:8000/examples
>>
>> > I suspect Twitter loads but they supposed to be load after document is
>> > ready, right?
>>
>> > On 11/21/10, Bruno Rocha  wrote:
>>
>> > > Windows firewall, browser security settings or some antivirus system?
>>
>> > > 2010/11/20 Carlos 
>>
>> > >> Hi,
>>
>> > >> Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
>> > >> often take a LOOONG time to load web2py urls in the following
>> > >> format?:
>>
>> > >>  http://127.0.0.1:8000/
>>
>> > >> I just see in the following in the status bar:
>>
>> > >>   Waiting forhttp://127.0.0.1:8000/...
>>
>> > >> Even after trying to refresh/reload many times, and then all of the
>> > >> sudden everything work ok, until the delays occur again !
>>
>> > >> When using Chrome, I never have to wait, there are no delays, and
>> > >> everything is very fast.
>>
>> > >> I'm using web2py 1.89.1 source on win7.
>>
>> > >> Any ideas?.
>>
>> > >> Thanks,
>>
>> > >>   Carlos
>>
>> > > --
>>
>> > > Bruno Rocha
>> > >http://about.me/rochacbruno/bio

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Carlos]

This issue is not related to any extra/ajax loading (e.g. in admin or
so), I've tried it with everything: admin, appadmin, welcome, my app,
etc., same long delay.

The load takes about one full minute !

Strangely it only occurs *intermitently* in IE and Firefox, but Chrome
(and maybe Opera) work ok all the time.

I use AVG free antivirus.

Any other info I should provide?, any other ideas?.

Thanks,

   Carlos


On Nov 20, 8:33 pm, mdipierro  wrote:
> yes. the twitten part is loaded via ajax. Should not cause the delay.
>
> On Nov 20, 8:10 pm, Phyo Arkar  wrote:
>
>
>
>
>
>
>
> > I got very long loading time on examples ., it just waiting for (about
> > 10-15 seconds) and do nothing.http://127.0.0.1:8000/examples
>
> > I suspect Twitter loads but they supposed to be load after document is
> > ready, right?
>
> > On 11/21/10, Bruno Rocha  wrote:
>
> > > Windows firewall, browser security settings or some antivirus system?
>
> > > 2010/11/20 Carlos 
>
> > >> Hi,
>
> > >> Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> > >> often take a LOOONG time to load web2py urls in the following format?:
>
> > >>  http://127.0.0.1:8000/
>
> > >> I just see in the following in the status bar:
>
> > >>   Waiting forhttp://127.0.0.1:8000/...
>
> > >> Even after trying to refresh/reload many times, and then all of the
> > >> sudden everything work ok, until the delays occur again !
>
> > >> When using Chrome, I never have to wait, there are no delays, and
> > >> everything is very fast.
>
> > >> I'm using web2py 1.89.1 source on win7.
>
> > >> Any ideas?.
>
> > >> Thanks,
>
> > >>   Carlos
>
> > > --
>
> > > Bruno Rocha
> > >http://about.me/rochacbruno/bio

Re: [web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[Luis Díaz]

I had a similar problem and was produced by my work poxy

if you are behind a proxy, I recommend you disable it in your browser while
you do local tests.

--
google translator

-- 
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo

http://web2pyfacil.blogspot.com/
Facultad de 
Odontología

[web2py] Re: very long wait for http://127.0.0.1:8000/ on IE and Firefox browsers

[mdipierro]

yes. the twitten part is loaded via ajax. Should not cause the delay.

On Nov 20, 8:10 pm, Phyo Arkar  wrote:
> I got very long loading time on examples ., it just waiting for (about
> 10-15 seconds) and do nothing.http://127.0.0.1:8000/examples
>
> I suspect Twitter loads but they supposed to be load after document is
> ready, right?
>
> On 11/21/10, Bruno Rocha  wrote:
>
> > Windows firewall, browser security settings or some antivirus system?
>
> > 2010/11/20 Carlos 
>
> >> Hi,
>
> >> Why do IE (v. 8) and Firefox (v. 3.6 with Firebug) browsers quite
> >> often take a LOOONG time to load web2py urls in the following format?:
>
> >>  http://127.0.0.1:8000/
>
> >> I just see in the following in the status bar:
>
> >>   Waiting forhttp://127.0.0.1:8000/...
>
> >> Even after trying to refresh/reload many times, and then all of the
> >> sudden everything work ok, until the delays occur again !
>
> >> When using Chrome, I never have to wait, there are no delays, and
> >> everything is very fast.
>
> >> I'm using web2py 1.89.1 source on win7.
>
> >> Any ideas?.
>
> >> Thanks,
>
> >>   Carlos
>
> > --
>
> > Bruno Rocha
> >http://about.me/rochacbruno/bio
>
>