Bugzilla – Full Text Bug Listing
| Summary: | Web interface very slow | ||
|---|---|---|---|
| Product: | Community | Reporter: | Steve Powell <zteve.powell> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Steve Powell
I'm seeing 1.3 s to load the home page from my home cable connection, and 0.8s to load the Hudson home page from Amazon ec2. Logged in, load times are very fast for me. (In reply to comment #1) > I'm seeing 1.3 s to load the home page from my home cable connection, and 0.8s > to load the Hudson home page from Amazon ec2. Logged in, load times are very > fast for me. I'm logged in. Not that that should be a problem. My colleagues experience the same sluggishness -- we are talking about 10 or more seconds to start rendering a page, much longer for complex pages like configuration of jobs (which tend to restructure quite a bit after first render). Perhaps there are some logs you can look at? My real ip address is 89.21.231.34. This problem has started happening today (previous experience is much better); last usage (probably) Friday last week; when no (significant) problem found. This might help you to locate cause. > This might help you to locate cause.
Well, I can't reproduce it from the outside, and you're the only one reporting this.. I think I've located the cause :-)
The response times are now adequate once again. It is not clear from this bug log that anything specific was done to achieve this or to determine cause. Regards, The Cause. Since I could not reproduce this from two separate external locations, my determination was that the problem was not at our end, so no action was taken. I'm glad everything is working out now, though. For reference, a tcp traceroute (not icmp) would have been helpful in identifying if (and where) the problem was network congestion. traceroute -T build.eclipse.org -p 443 Thank you. For reference: your suggested command is not consistent with the traceroute I have on my platform: traceroute [-adeFISdNnrvx] [-A as_server] [-f first_ttl] [-g gateway] [-i iface] [-M first_ttl] [-m max_ttl] [-P proto] [-p port] [-q nqueries] [-s src_addr] [-t tos] [-w waittime] [-z pausemsecs] host [packetsize] What would I type here? OK I typed: traceroute -p 443 build.eclipse.org and got... traceroute to build.eclipse.org (206.191.52.57), 64 hops max, 52 byte packets 1 31.fa3-0.er01.sotsci.vostron.net (89.21.231.33) 1.161 ms 0.830 ms 0.743 ms 2 200.gi0-0.thelon-pe01.vostron.net (89.21.224.5) 5.984 ms 6.672 ms 5.732 ms 3 gi1-24.telehouse-east.core.enta.net (78.33.30.53) 5.984 ms 6.008 ms 5.729 ms 4 gwy1-nyc.bb.allstream.net (195.66.225.30) 98.429 ms 97.683 ms 98.425 ms 5 ge-wan-4-1.hcap4-ott.bb.allstream.net (199.212.172.18) 124.716 ms 199.114 ms 200.358 ms 6 66.46.220.198 (66.46.220.198) 115.921 ms 116.559 ms 116.160 ms 7 gateway2-vlan94.magma.ca (209.217.64.49) 116.424 ms 115.076 ms 114.670 ms 8 206.191.0.120 (206.191.0.120) 114.916 ms 115.319 ms 117.164 ms 9 * * * 10 * * * . . 64 * * * and there we stop (of course). I'm not sure what is going on. Well, the problem dissipated... |