httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Behlendorf <>
Subject Apache user survey
Date Sat, 13 Dec 1997 01:20:03 GMT

I'd really like us, the developers, to get a better sense of who's using
Apache, what they're using it for, what they like and don't like about it,
and what the user base thinks would be good in terms of future features and
priorities.  Given that as a volunteer project we're a whole lot less
beholden to these types of things than a commercial company; yet several of
us here are reliant upon Apache for commercial reasons, and I think for the
others this would be very useful to have.  Trying to gauge this information
from the bugdb and newsgroups is like trying to determine how good a movie
is based on the amount of popcorn on the floor afterwards :)

So, here's some questions I'd like to ask on a survey.  It would be set up
as a web form on, with notice sent to apache-announce and
c.i.w.s.*.  We'd collect data for a few weeks and then analyse it, and make
the results public.  Feedback on these questions plus additional ones would
be cool.  It's certainly very rough and a few questions could use some
additional answers as options.  I'd be really happy if we got 1000 responses.

A challenge is to figure out how to motivate folks to answer these
questions.  Hmm.  Organic might be willing to chip in for some sort of
prize to be raffled off, maybe a free copy of Stronghold?


(Deployment questions - to figure out how to interpret #'s from Netcraft)

How many different installations of Apache are you responsible for?
  (break out #'s amongst OS's: Solaris, Linux, FreeBSD, NT, Irix, HP, etc)

How many of these installations are on multiple-CPU machines?

How many total IP numbers do you have Apache configured to listen on?
  _##_ available to the open internet
  _##_ available only to internal users behind a firewall

How much raw traffic (measured in hits) per week does your server get?
  (1-10K, 10K-100K, 100K-1M, 1M-10M, 10M-100M, 100M+)

Describe your purpose for your web sites:  (check all that apply)
  (ISP, corporate public web pages, intranet, experimentation,
   proxy, personal home page, non-profit organization)

(Use of optional features)

Do you currently use the "suexec" functionality in Apache?

Which non-standard modules do you currently use in your production 
  web environments?
(include, proxy, rewrite, usertrack, expires, headers, mime_magic, 
  status, info, speling, unique_id)

Which related packages do you use with Apache? (list major add-ons)
(mod_perl, mod_php, mod_jserv, mod_auth_mysql, mod_ldap, mod_pyapache)

For what strong reasons do you use Apache over other web servers?  
Check if you agree with the statement made. (check all that apply)
   It serves up pages faster than other servers.
   I can configure it to do many different things; it's very flexible.
   Its reliability is high.
   I have access to the source code.
   I like the terms of the Apache license.
   It is ported to the platform you use.
   It has features other servers don't have.
   It has a very wide userbase.
   It has many add-on modules.
   It is easy to configure.
   I think it's less likely to have a significant security hole, 
     and if there's one it can be quickly fixed with a source 
     code patch.
   I want to support the idea of "free" software.

Which module do you use to build server-side applications?  Check 
  those you use most heavily.
(mod_cgi, mod_include, mod_perl, mod_php, mod_jserv, others?)

Do you use a commercial hybrid of Apache?  if so, which ones?
(StrongHold, WebTen, WarPaint, others?)

Do you use Apache with relational or object-oriented databases?  
  If so, which ones?
(Oracle, Sybase, Informix, msql, mysql, Velocis, ODI, others?)

What third-party tools do you use behind Apache?
(Vignette's StoryServer, Apple's WebObjects, NetObjects, ColdFusion, 
iCat, others?)

Do you currently pay a consultant or company to provide commercial 
support for Apache?

(what's missing?)

Please indicate to what extent you agree with the following statements.  
(five possible positions for each question, ranging from "strongly 
agree" to "strongly disagree")

Apache would be more valuable to me if:
  * it was as complete on NT as other NT web servers.
  * it had better support for server-side Java.
  * it had a simpler API.
  * it had a standard web-based graphical user interface.
  * it had a java-based GUI.
  * it had a "native windowing system" GUI.
  * it integrated more easily with third-party tools.
  * it was multithreaded, so it would be faster.
  * it was multithreaded, so I could write multithreaded applications 
    behind it.
  * it was multithreaded, so I could hook it up directly to other 
    existing multithreaded applications.
  * it was multithreaded, so it would use less memory.  
  * it had a revamped configuration file language.
  * its internals were written in C++ instead of C.
  * it had better documentation.
  * there were more books on Apache.
  * there were classes offered on Apache maintenance and programming.
  * the bug reporting database was easier to use.
  * commercial support was easier to find.
  * there was better release packaging.
  * others?

If you were in the market for commercial support for Apache, what would 
  be an appropriate price point for quality service?
On a per-machine, per-month basis:  ($1-100, 100-300, 300-500, 500-1000,
On a per-incident basis:  ($1-50, 50-100, 100-150, 150-200, 200+)

Let me know what you think.


"it's a big world, with lots of records to play."-sig

View raw message