Well, maybe this one is out of topic but anyway... I always wanted to have Cherokee in Irix, so after a while in front of my SGI O2, edit some source files, touch configure, and deal with getopt_long (), I was able to achieve a static-build of cherokee 0.7.2. This could build run smoothly (although cherokee-config hung up shortly after launch cherokee, but the HTTP server is still running).
The binary is here: http://bsdero.gulags.org.mx/index.php#english_cherokee_irix Maybe it can be on the "downloads" section. I dont know if this build is useful for someone, but if so, it will runs very well in a Tezro, Octane or any SGI computer more powerful than my little O2. By the way, this version is compiled with nekoware GCC. By the way, I touch some source codes and the configure.in script, maybe I can commit this changes? I'll try to do a compile & running of current sources from svn... On 7/25/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send Cherokee mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.octality.com/listinfo/cherokee > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cherokee digest..." > > > Today's Topics: > > 1. Re: Introduction (Stefan de Konink) > 2. Re: Introduction (Gunnar Wolf) > 3. Re: Cherokee 0.8.0 quick update (Gunnar Wolf) > 4. Re: Cherokee 0.8.0 quick update (Stefan de Konink) > 5. Re: Introduction (Alvaro Lopez Ortega) > 6. Re: Cherokee 0.8.0 quick update (Alvaro Lopez Ortega) > 7. Re: Cherokee 0.8.0 quick update (Alvaro Lopez Ortega) > 8. Re: Cherokee 0.8.0 quick update (Stefan de Konink) > 9. I/O Bottleneck Verbage (M. David Peterson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 25 Jul 2008 00:36:21 +0200 > From: Stefan de Konink <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Introduction > To: Gunnar Wolf <[EMAIL PROTECTED]> > Cc: cherokee-list <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Gunnar Wolf schreef: >> Milo van der Linden dijo [Thu, Jul 24, 2008 at 08:21:55PM +0200]: >>> I have a virtual machine ready with the latest svn cherokee, lighttpd >>> and apache to rerun the benchmarks. I am only waiting for the 0.8.0 to >>> reach stable. Then I hope the new benchmarks will find their way to the >>> website. I have automated the installation script for >>> cherokee/apache/lighttpd. It can be re-run with every new release ;-) >>> Hope that partially answers one of the questions. >> >> Virtual machines should be avoided when testing for performance - you >> are incurring on the penalties of competing for resources _twice_ (on >> each OS layer). If you want to give true statistics, do it as close as >> possible to the metal! > > The method I proposed before was using some old machines (aka 486/PII) > and allowing a fixed amount of time of requests. The slower the machine > the better. > > But there is one thing in VMs that are actually very cool. That is the > amount of cpu cycles used. So instead of of 10 seconds of requests, you > could actually do 50000 request, and check the CPU usage for each > implementation. > > It is not about the maximum performance on a Dell1950, because a kernel > can make a difference. It is how much performance is required to deliver > peak performance. > > > Stefan > > > ------------------------------ > > Message: 2 > Date: Thu, 24 Jul 2008 17:41:10 -0500 > From: Gunnar Wolf <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Introduction > To: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Cc: cherokee-list <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > Alvaro Lopez Ortega dijo [Thu, Jul 24, 2008 at 08:43:38PM +0200]: >> >>> //1//- Monitoring website behaviour might be useful (2 comments >> >>> including mine), but we prefer not to use Google (2 comments). >> >> >> >> Honestly, as far as the Cherokee project is concerned, tracking using >> >> behavior is a red herring. It's a distraction from what matters most: >> >> The number of active installations in use on the web. >> >> Completely agree. +1. > > If the webserver world were composed exclusively of Debian machines, > all of them running popcon, this would be even more interesting to > you. Still, > > http://qa.debian.org/popcon.php?package=cherokee > http://qa.debian.org/popcon.php?package=apache2 > http://qa.debian.org/popcon.php?package=lighttpd > http://qa.debian.org/popcon.php?package=boa > http://qa.debian.org/popcon.php?package=nginx > http://qa.debian.org/popcon.php?package=thttpd > > There are many other HTTP servers in Debian, of course... Those are > the ones I got off the tip of my head. > > -- > Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 > PGP key 1024D/8BB527AF 2001-10-23 > Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF > > > ------------------------------ > > Message: 3 > Date: Thu, 24 Jul 2008 17:43:42 -0500 > From: Gunnar Wolf <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Cherokee 0.8.0 quick update > To: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Cc: Cherokee Mailing List <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > Alvaro Lopez Ortega dijo [Fri, Jul 25, 2008 at 12:35:04AM +0200]: >> >Debian is going to freeze the next stable release this week. We are >> >currently including Cherokee 0.7.2-3 (all of the patches I've applied >> >to the tree have been also sent to ?lvaro, and are said to be applied >> >to the SVN tree). >> > >> >Is there some _really_ pressing reason I should try to push 0.8.x in >> >Lenny? I would strongly prefer not doing so, as there is a reason for >> >the testing period. >> >> Cherokee 0.8.0-pre does not include many new features. However, >> there is a quite big difference regarding the performance and the >> stability under very heavy loads. >> >> Actually, I'd vote for going with 0.8.0-pre instead of >> 0.7.2. Please, let me know whether a 0.8.0-pre1 release would be >> helpful. If so, I will release it within tomorrow. > > Ok - But are you _sure_ it's not worse stability-wise? I can do a high > priority upload (which might get accepted in time, but I cannot assure > you - we are quite close to the deadline!). I'm just about to go > offline for several days, but I can try and build+upload tomorrow > early before leaving. > > -- > Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 > PGP key 1024D/8BB527AF 2001-10-23 > Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF > > > ------------------------------ > > Message: 4 > Date: Fri, 25 Jul 2008 00:46:00 +0200 > From: Stefan de Konink <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Cherokee 0.8.0 quick update > To: Gunnar Wolf <[EMAIL PROTECTED]> > Cc: Cherokee Mailing List <[EMAIL PROTECTED]>, Alvaro > Lopez Ortega <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Gunnar Wolf schreef: >> Ok - But are you _sure_ it's not worse stability-wise? I can do a high >> priority upload (which might get accepted in time, but I cannot assure >> you - we are quite close to the deadline!). I'm just about to go >> offline for several days, but I can try and build+upload tomorrow >> early before leaving. > > > Someone *please* check if basic CGI works out of the box :) > > > Stefan > > > > ------------------------------ > > Message: 5 > Date: Fri, 25 Jul 2008 00:45:31 +0200 > From: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Introduction > To: Gunnar Wolf <[EMAIL PROTECTED]> > Cc: cherokee-list <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > On 25 Jul 2008, at 00:31, Gunnar Wolf wrote: > >> Quite unrelated to the site, but related to webpages (if that's what >> you are familiar with): It would be very good if you could put some >> work into the cherokee-admin webpages, adding some Javascripty >> niceties to avoid the user losing his changes because he didn't click >> on 'save'. Maybe even just a simple alertbox would do - or you could >> go the whole AJAX way and send each individual change to the server as >> it happens (it would be too much, IMHO), or an automatic submit when >> the user navigates away, or... whatever you fancy ;-) > > > Huge +1 for this. > > Even if many of us have learned to live with the usability issue that > Gunnar is talking about, they should be resolved ASAP. I'd dare to say > that they should be marked as high priority for Cherokee 0.9.0. > > The bottom line is: Cherokee includes cherokee-admin just to make > users life easier, if it weren't easy to use, natural, and coherent, > we would have failed even after having put a whole lot of work on it. > > -- > Greetings, alo. > http://www.alobbs.com/ > > > > ------------------------------ > > Message: 6 > Date: Fri, 25 Jul 2008 00:51:24 +0200 > From: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Cherokee 0.8.0 quick update > To: Gunnar Wolf <[EMAIL PROTECTED]> > Cc: Cherokee Mailing List <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > On 25 Jul 2008, at 00:43, Gunnar Wolf wrote: >> Alvaro Lopez Ortega dijo [Fri, Jul 25, 2008 at 12:35:04AM +0200]: >>>> Debian is going to freeze the next stable release this week. We are >>>> currently including Cherokee 0.7.2-3 (all of the patches I've >>>> applied >>>> to the tree have been also sent to ?lvaro, and are said to be >>>> applied >>>> to the SVN tree). >>>> >>>> Is there some _really_ pressing reason I should try to push 0.8.x in >>>> Lenny? I would strongly prefer not doing so, as there is a reason >>>> for >>>> the testing period. >>> >>> Cherokee 0.8.0-pre does not include many new features. However, >>> there is a quite big difference regarding the performance and the >>> stability under very heavy loads. >>> >>> Actually, I'd vote for going with 0.8.0-pre instead of >>> 0.7.2. Please, let me know whether a 0.8.0-pre1 release would be >>> helpful. If so, I will release it within tomorrow. >> >> Ok - But are you _sure_ it's not worse stability-wise? I can do a high >> priority upload (which might get accepted in time, but I cannot assure >> you - we are quite close to the deadline!). I'm just about to go >> offline for several days, but I can try and build+upload tomorrow >> early before leaving. > > IMO, it's worth trying. Cherokee 0.8.0-pre is clearly ahead of 0.7.2 > on many ways (mainly performance and stability). > > Would you need me to release a 0.8.0-pre1?.. or, would the auto- > uploaded tarball be enough for this? > http://www.cherokee-project.com/download/trunk/ > > Cheers! > > -- > Greetings, alo. > http://www.alobbs.com/ > > > > ------------------------------ > > Message: 7 > Date: Fri, 25 Jul 2008 01:02:35 +0200 > From: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Cherokee 0.8.0 quick update > To: Stefan de Konink <[EMAIL PROTECTED]> > Cc: Cherokee Mailing List <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > On 25 Jul 2008, at 00:46, Stefan de Konink wrote: >> Gunnar Wolf schreef: >>> Ok - But are you _sure_ it's not worse stability-wise? I can do a >>> high >>> priority upload (which might get accepted in time, but I cannot >>> assure >>> you - we are quite close to the deadline!). I'm just about to go >>> offline for several days, but I can try and build+upload tomorrow >>> early before leaving. >> >> Someone *please* check if basic CGI works out of the box :) > > Of course it does... why wouldn't it? :-) > > The default configuration file points the '/cgi-bin' web directory to > '/usr/lib/cgi-bin/' for executing CGIs. So, if you install any package > shipping CGIs, they ought to work out of the box. > > Actually, a few hours ago I installed a new server running Mailman > (one of the last CGI based applications?), and the interface appeared > magically at http://server/cgi-bin/mailman/listinfo right after > installing the package. > > -- > Greetings, alo. > http://www.alobbs.com/ > > > > ------------------------------ > > Message: 8 > Date: Fri, 25 Jul 2008 01:21:41 +0200 (CEST) > From: Stefan de Konink <[EMAIL PROTECTED]> > Subject: Re: [Cherokee] Cherokee 0.8.0 quick update > To: Alvaro Lopez Ortega <[EMAIL PROTECTED]> > Cc: Cherokee Mailing List <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Fri, 25 Jul 2008, Alvaro Lopez Ortega wrote: > >> > Someone *please* check if basic CGI works out of the box :) >> >> Of course it does... why wouldn't it? :-) > > Because last time *I* checked from svn, it was only compiled when I did > --enable-beta, that was one of the reasons why the cherokee-admin broke > for me. > > > Stefan > > > > ------------------------------ > > Message: 9 > Date: Thu, 24 Jul 2008 23:28:19 -0600 > From: "M. David Peterson" <[EMAIL PROTECTED]> > Subject: [Cherokee] I/O Bottleneck Verbage > To: cherokee-list <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 > > I find the following verbiage at http://cherokee-project.com a little > strange: > >>> One of the intended objectives is being able to turn the server's hard >>> drive into the effective bottleneck of the system. That is a lot. With >>> each release we get closer to our goal. Admittedly, a very tough goal >>> to reach. After that there's really not much left to do to improve a >>> High Performance web server such as Cherokee. << > > In particular: > > "After that there's really not much left to do to improve a High > Performance web server such as Cherokee." > > The above places a specific shelf-life on the Cherokee project as far as > innovation is concerned. While I recognize the reasoning, placing the > hard drive at the center of I/O operations seems to neglect the fact that > we're well into the transition between magnetic media and RAM-based > distributed storage (e.g. memcached), using the hard drive as nothing more > than a long term storage system. AKA, Magnetic Drives are the new Tape. > > Could I suggest a rewrite of the above to something similar to: > >>> The speed at which any web server can serve requests for content is >>> both directly tied to and limited by the I/O speed of underlying >>> hardware and operating system. In this regard, a web servers >>> performance is measured by the latency incurred after an I/O request to >>> the underlying system has completed. > > The primary objective of the Cherokee project is to reduce to zero the > latency incurred between the time a dynamic or static system I/O request > has completed and the time the resulting content is served to the > requesting client. Admittedly, a very tough goal to reach. In fact, it > might be impossible. But achieving that which was once seen as impossible > is what drives innovation. And it's innovation that drives the ongoing > development of the Cherokee project, bringing us closer to the impossible > with each new release. << > > ? > > Okay, that last parts a little cheesy, and even the first part is only a > suggestion. But placing a shelf life on project innovation isn't what I > would term a strong elevator pitch, which is exactly what those first two > paragraphs represent. > > Keep up the great work! :D > > -- > /M:D > > M. David Peterson > Co-Founder & Chief Architect, 3rd&Urban, LLC > Email: [EMAIL PROTECTED] | [EMAIL PROTECTED] > Mobile: (206) 999-0588 > http://3rdandUrban.com | http://amp.fm | > http://www.oreillynet.com/pub/au/2354 | > http://news.oreilly.com/m-david-peterson/ > > > ------------------------------ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > > End of Cherokee Digest, Vol 1, Issue 4 > ************************************** > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
