Just downloaded last stable realease of web2py source version (2.4.6) on my linux machine (Archlinux 64bit on Inter Core2 Duo 2GHz and 4GB RAM). Launching web2py from console via
$ python2.7 ./web2py.py requires just a little less than 25 second before to show the server configuration interface (the TK widget) after inserting the password (the browser is already opened to minimize delays) it will require (again) about 25 seconds before the page 127.0.0.1:8000 is served. After that, everything works normal with no more delays. Only the startup is really slow. On the same machine within a virtualboxed windows XP with the same version of web2py everything works as usually with no sensible delays (about 2 secs before tk widget and before first page is served) Launching web2py with wingide, which permits to set breakpoint and the execution step by step, I've found that the line that requires almost all of the 25 seconds before the TK widget is: ---8<--- gluon/widget.py : 1054 (options, args) = console() ---8<--- which is slowed down by ---8<--- gluon/widget.py: 919-921 options.ips = list(set([ ip[4][0] for ip in socket.getaddrinfo(socket.getfqdn(), 0) if not is_loopback_ip_address(ip[4][0])])) ---8<--- which finds all the network interfaces (non loopback) on wich web2py could listen/serve Even if I specify ip address on the command line, this loop is executed anyhow. Any suggestion to make the startup faster ? (actually from launch to first page served is about 55-60 seconds) Or should I resign to wait ? (not a big hassle, if you know it in advance ;-) ) Thanks, Andrea -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
<<attachment: Screenshot - 04222013 - 09:54:54 PM.png>>
