You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Behlendorf <br...@collab.net> on 2001/01/27 05:54:12 UTC
"because it's christmas"
[taz3] 8:10pm ~ > telnet apache.org 80
Trying 64.208.42.41...
Connected to apache.org.
Escape character is '^]'.
HEAD / HTTP/1.0
HTTP/1.1 200 OK
Date: Sat, 27 Jan 2001 04:10:28 GMT
Server: Apache/2.0b1-dev (Unix)
Last-Modified: Tue, 09 Jan 2001 19:00:04 GMT
ETag: "24d0e-1503-c1105500"
Accept-Ranges: bytes
Content-Length: 5294
Connection: close
Content-Type: text/html
Tada! Thanks to the patches made after the last run (fixing the byterange
requests on HEAD, etc) and some help from gregames, the new server is
running on port 80 on apache.org. The only two things not working on the
last server are Tomcat (now relayed directly to Tomcat's built-in HTTP
server on port 8080) and ExtendedStatus. It's using the prefork mpm, so
it's not quite testing the multithreading stuff, but I'd like to try that
next. As it is, it's quite stable, and even to me, perceptably faster - I
use the home page for xml.apache.org as a benchmark thanks to the insane
number of inlined images. =)
I'm going to try leaving it running for the evening, making sure it can
get restarted appropriately at midnight when we roll the logfiles. If
people want to help monitor its health, tail the error_log, at
/logs/www/error_log. Especially, if someone from each project could look
through that error log at all the broken links and start addressing them,
that would help at least reduce the noise in that log.
So far I've seen only one core file, I'll be collecting them and keeping
them in /usr/local/apache2 if anyone wants to look through them. New ones
get deposited in /tmp.
Anyways, congrats to the whole 2.0 team for progress so far. =)
Brian
Re: "because it's christmas"
Posted by Brian Behlendorf <br...@collab.net>.
On Sat, 27 Jan 2001, William A. Rowe, Jr. wrote:
> Brian, could we set up 1.3.x in parallel on a higher port? I would swear the
> entire site is noticably faster than it once was, but load/traffic/congestion
> throws in too many variables. It would be fun to pull down /docs/misc/FAQ.html
> from both httpd.apache.org and httpd.apache.org:1300 at the same time, and
> actually see the difference.
I'm fine with using apache.org as something of a guinea pig w/r/t finding
seg faults and other problems, but I really don't want to encourage people
to do benchmarking against it, especially because of the variables
you mention.
Brian
Re: "because it's christmas"
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
From: "Brian Behlendorf" <br...@collab.net>
Sent: Friday, January 26, 2001 10:54 PM
> Tada! Thanks to the patches made after the last run (fixing the byterange
> requests on HEAD, etc) and some help from gregames, the new server is
> running on port 80 on apache.org. The only two things not working on the
> last server are Tomcat (now relayed directly to Tomcat's built-in HTTP
> server on port 8080) and ExtendedStatus. It's using the prefork mpm, so
> it's not quite testing the multithreading stuff, but I'd like to try that
> next. As it is, it's quite stable, and even to me, perceptably faster - I
> use the home page for xml.apache.org as a benchmark thanks to the insane
> number of inlined images. =)
Brian, could we set up 1.3.x in parallel on a higher port? I would swear the
entire site is noticably faster than it once was, but load/traffic/congestion
throws in too many variables. It would be fun to pull down /docs/misc/FAQ.html
from both httpd.apache.org and httpd.apache.org:1300 at the same time, and
actually see the difference.
Bill