Re: Performance tuning documentation

On Nov 12, 2009, at 8:30 AM, Rich Bowen wrote:

> The performance tuning documentation that we currently include in the docs is simply awful. What with the
comments about Apache 1.2 and the suggestions of how to deal with the new Linux 2.0 kernel, I think it's
beyond fixing. It needs to be tossed and rewritten - although perhaps there are parts that are salvageable.
> 
> I was wondering if someone has a performance doc that they could contribute as a starting place? Perhaps
Sander's talk from AC? Or if someone would be willing to give some attention to the docs list for a while to
assist in writing something that would be useful to actual admins in the real world.

I am willing to contribute my performance talk material, since I don't really give that presentation
anymore.  I have very few cycles, but would be willing to help work on making it suitable for inclusion in the
httpd docs.  

Over the years, I have tried to concentrate more on the tuning knobs available to the average admin, rather
than dig into the operating system or httpd code.  

Another source may be Colm's talks, but he is still giving those.  

S.

--

-- 
sander <at> temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

Re: svn commit: r906779 - /httpd/httpd/trunk/docs/manual/configuring.xml

On Fri, Feb 5, 2010 at 7:51 AM, Dan Poirier <poirier <at> pobox.com> wrote:
> [Moving discussion from dev <at>  to docs <at> httpd.apache.org]
>
> On Fri, Feb  5, 2010, at 06:57:58 AM, Jeff Trawick <trawick <at> gmail.com> wrote:
>
>> On Thu, Feb 4, 2010 at 9:48 PM,  <poirier <at> apache.org> wrote:
>>> +    <p>Only environment variables defined before the server is started
>>> +    can be used in expansions.  Variables defined in the
>>> +    configuration file itself, for example with <directive
>>> +    module="mod_env">SetEnv</directive>, take effect too late to be
>>> +    used for expansions in the configuration file.</p>
>>
>> I think the "take effect too late..." wording supports the common
>> confusion that OS-level environment variables and those server
>> variables that are set in the environment of sub-processes are
>> essentially the same thing.
>>
>> I don't know what the magic distinguishing words are.  Perhaps "OS
>> environment variable," with a link to a new glossary entry, should be
>> used in the appropriate places?  The glossary entry for Environment
>> variable describes the difference but doesn't introduce unique
>> terminology for the two types of variables
>> (http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
>
> I agree that it's still ambiguous or even misleading. I played with
> trying to expand on that, but couldn't come up with wording I liked last
> night.
>
> It would definitely help to have unique terminology.  Maybe "operating
> system environment variables" for the ones set outside the server in the

Re: Performance tuning documentation

----- "Sander Temme" <sander <at> temme.net> wrote:

> On Nov 12, 2009, at 8:30 AM, Rich Bowen wrote:
> 
> > The performance tuning documentation that we currently include in
> the docs is simply awful. What with the comments about Apache 1.2 and
> the suggestions of how to deal with the new Linux 2.0 kernel, I think
> it's beyond fixing. It needs to be tossed and rewritten - although
> perhaps there are parts that are salvageable.

There are a few parts that might still be usable, like the choice of
the MPM. 

> I am willing to contribute my performance talk material, since I don't
> really give that presentation anymore.  I have very few cycles, but
> would be willing to help work on making it suitable for inclusion in
> the httpd docs.  

Unfortunately, I've never been at any of your talks. I hope I'm not
leaning too far out the window with my suggestion here

> Over the years, I have tried to concentrate more on the tuning knobs
> available to the average admin, rather than dig into the operating
> system or httpd code.  

I've been wondering: httpd is very complex. It can be an

* Application Server, serving SSI, CGI, PHP, Perl, Ruby, Python...
* SSL-Off-loading, Caching reverse-proxy that understands

mod_status update

Hi folks,

due to the everlasting confusion on #httpd as to what this ominous "CPU Usage" means
in /server-status, I took a look at the source and documented it.

I unified the looks of split-logfile and log_server_status, by introducing
<code> elements around the <a>s.

And finally I documented the fact that log_server_status is a very simple program,
which might fail in a complex setup.

This is a diff against trunk.

So long,
--

-- 
Igor Galić

Tel: +43 (0) 699 122 96 338
Fax: +43(0) 1 91 333 41
Mail: i.galic <at> brainsware.org
URL: http://brainsware.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

is there an archive for this list ?

Hi,

I have just joined this list.

Is there an archive of previous discussions ?

regards,
Martin

Re: is there an archive for this list ?

On 15 February 2010 12:13, Martin Waite <waite.134 <at> googlemail.com> wrote:
> Hi,
>
> I have just joined this list.
>
> Is there an archive of previous discussions ?
>
> regards,
> Martin
>
Hi,

I found the archive in

http://httpd.apache.org/lists.html#http-docs

I was confused by the doc-help message which does not indicate that
there is an archive.

Please ignore.

regards,
Martin

mod_fcgid (HEAD) spewing "too much processes, please increase FCGID_MAX_APPLICATION"; no documentation/guidance available on FCGID_MAX_APPLICATION

I'm running,

httpd2 -V
	Server version: Apache/2.2.14 (Linux/SUSE)
	Server built:   Feb 19 2010 19:43:22
	Server's Module Magic Number: 20051115:23
	Server loaded:  APR 1.3.8, APR-Util 1.3.9
	Compiled using: APR 1.3.8, APR-Util 1.3.9
	Architecture:   32-bit
	Server MPM:     Worker
	  threaded:     yes (fixed thread count)
	    forked:     yes (variable process count)
	Server compiled with....
	 -D APACHE_MPM_DIR="server/mpm/worker"
	 -D APR_HAS_SENDFILE
	 -D APR_HAS_MMAP
	 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
	 -D APR_USE_SYSVSEM_SERIALIZE
	 -D APR_USE_PTHREAD_SERIALIZE
	 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
	 -D APR_HAS_OTHER_CHILD
	 -D AP_HAVE_RELIABLE_PIPED_LOGS
	 -D DYNAMIC_MODULE_LIMIT=128
	 -D HTTPD_ROOT="/srv/www"
	 -D SUEXEC_BIN="/usr/sbin/suexec2"
	 -D DEFAULT_PIDLOG="/var/run/httpd2.pid"
	 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
	 -D DEFAULT_ERRORLOG="/var/log/apache2/error_log"
	 -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types"
	 -D SERVER_CONFIG_FILE="/etc/apache2/httpd.conf"