[haiku-development] Re: Trac Almost Unusable
- From: Marcus Overhagen <marcusoverhagen@xxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 6 Feb 2008 23:00:21 +0100 (CET)
Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> lately (not sure when it started exactly) Trac has become extremely slow
> for me. It often takes 30 seconds or more (and virtually never under 10
> seconds) to get a response to an action. Sometimes I get a "Proxy Error"
> instead. I don't know, if others have similar problems, but at least for me
I noticed the same problem. Proxy errors (but I'm not using any proxy!), slow
load, etc.
See below for some examples. Opening a ticket takes 17 seconds. Baaaah!
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /ticket/1723.
Reason: Error reading from remote server
marcus@dagobert:~$ time wget http://dev.haiku-os.org/ticket/1723#comment:9
--22:54:03-- http://dev.haiku-os.org/ticket/1723
=> `1723'
Resolving dev.haiku-os.org... 66.98.214.35
Connecting to dev.haiku-os.org|66.98.214.35|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13,341 (13K) [text/html]
100%[===================================>] 13,341 42.09K/s
22:54:20 (41.87 KB/s) - `1723' saved [13341/13341]
real 0m17.248s
user 0m0.000s
sys 0m0.004s
marcus@dagobert:~$ time wget http://dev.haiku-os.org/timeline
--22:51:48-- http://dev.haiku-os.org/timeline
=> `timeline'
Resolving dev.haiku-os.org... 66.98.214.35
Connecting to dev.haiku-os.org|66.98.214.35|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 40,416 (39K) [text/html]
100%[=====================================>] 40,416 26.14K/s
22:51:56 (26.08 KB/s) - `timeline' saved [40416/40416]
real 0m8.605s
user 0m0.000s
sys 0m0.000s
marcus@dagobert:~$ ping dev.haiku-os.org
PING dev.haiku-os.org (66.98.214.35) 56(84) bytes of data.
64 bytes from web5.webfaction.com (66.98.214.35): icmp_seq=1 ttl=52 time=155 ms
64 bytes from web5.webfaction.com (66.98.214.35): icmp_seq=2 ttl=52 time=158 ms
64 bytes from web5.webfaction.com (66.98.214.35): icmp_seq=3 ttl=52 time=155 ms
64 bytes from web5.webfaction.com (66.98.214.35): icmp_seq=4 ttl=52 time=157 ms
--- dev.haiku-os.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 155.135/156.733/158.059/1.328 ms
marcus@dagobert:~$ time wget http://heise.de
--22:54:58-- http://heise.de/
=> `index.html'
Resolving heise.de... 193.99.144.80
Connecting to heise.de|193.99.144.80|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.heise.de/ [following]
--22:54:58-- http://www.heise.de/
=> `index.html'
Resolving www.heise.de... 193.99.144.85
Connecting to www.heise.de|193.99.144.85|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
[ <=>
] 46,631
--.--K/s
22:54:59 (414.84 KB/s) - `index.html' saved [46631]
real 0m0.375s
user 0m0.000s
sys 0m0.004s
marcus@dagobert:~$ ping heise.de
PING heise.de (193.99.144.80) 56(84) bytes of data.
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=1 ttl=249 time=25.5
ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=2 ttl=249 time=28.0
ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=3 ttl=249 time=25.9
ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=4 ttl=249 time=27.1
ms
--- heise.de ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 25.568/26.694/28.085/1.008 ms
marcus@dagobert:~$
Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT FÜR ALLE NEUEINSTEIGER
Jetzt bei Arcor: günstig und schnell mit DSL - das All-Inclusive-Paket
für clevere Doppel-Sparer, nur 29,95 Euro inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2
Other related posts:
