stas 02/05/12 09:38:32
Modified: src/docs/1.0/guide performance.pod
Log:
fix broken internal links
Revision Changes Path
1.12 +17 -16 modperl-docs/src/docs/1.0/guide/performance.pod
Index: performance.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/performance.pod,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- performance.pod 11 May 2002 11:54:44 -0000 1.11
+++ performance.pod 12 May 2002 16:38:32 -0000 1.12
@@ -2591,7 +2591,7 @@
There are very important OS parameters that you might want to change
in order to improve the server performance. This topic is
discussed in the section: L<Setting the Buffering Limits on Various
-OSes|guide::scenario/Setting_the_Buffering_Limits_on_>
+OSes|guide::scenario/Setting_the_Buffering_Limits_on_Various_OSs>
=head1 Performance Tuning by Tweaking Apache Configuration
@@ -2985,12 +2985,12 @@
Your children can share memory between them when the OS supports that.
You must take action to allow the sharing to happen - See L<Preload
Perl modules at server
-startup|guide::performance/Preloading_Perl_Modules_at_Serve>. If you do
-this, the chances are that your C<MaxClients> can be even higher. But
-it seems that it's not so simple to calculate the absolute number. If
-you come up with a solution please let us know! If the shared memory
-was of the same size throughout the child's life, we could derive a
-much better formula:
+startup|guide::performance/Preloading_Perl_Modules_at_Server_Startup>.
+If you do this, the chances are that your C<MaxClients> can be even
+higher. But it seems that it's not so simple to calculate the
+absolute number. If you come up with a solution please let us know!
+If the shared memory was of the same size throughout the child's life,
+we could derive a much better formula:
Total_RAM + Shared_RAM_per_Child * (MaxClients - 1)
MaxClients = ---------------------------------------------------
@@ -4497,10 +4497,11 @@
reference to an object, but even then it can be passed by value.
I strongly endorse L<Apache::Request (libapreq) - Generic Apache
-Request Library|guide::modules/Apache_Request_libapreq_Gen>. Its core is
-written in C, giving it a significant memory and performance benefit.
-It has all the functionality of C<CGI.pm> except the HTML generation
-functions.
+Request
+Library|guide::modules/Apache__Request__libapreq____Generic_Apache_Request_Library>.
+Its core is written in C, giving it a significant memory and
+performance benefit. It has all the functionality of C<CGI.pm> except
+the HTML generation functions.
=head2 Interpolation, Concatenation or List
@@ -4683,7 +4684,7 @@
processes would show only one entry or none at all, since they might
not serve the same requests as the others. For more hints see the
section "L<Run the server in single
-mode|general::control/Running_a_Server_in_Single_Proce>".
+mode|general::control/Running_a_Server_in_Single_Process_Mode>".
=head1 Improving Performance by Prevention
@@ -4974,7 +4975,7 @@
from
Growing|guide::performance/Preventing_Your_Processes_from_Growing> and
L<Limiting Other Resources Used by Apache Child
-Processes|guide::performance/Limiting_Other_Resources_Used_by>.
+Processes|guide::performance/Limiting_Other_Resources_Used_by_Apache_Child_Processes>.
=head2 Preventing Your Processes from Growing
@@ -5366,7 +5367,7 @@
=head2 Sending Plain HTML as Compressed Output
See L<Apache::GzipChain - compress HTML (or anything) in the
-OutputChain|guide::modules/Apache_GzipChain_compress_HTM>
+OutputChain|guide::modules/Apache__GzipChain___compress_HTML__or_anything__in_the_OutputChain>
=head2 Caching Components with HTML::Mason
@@ -5856,7 +5857,7 @@
Proxy gives you a great performance increase in most cases. It's
discussed in the section L<Adding a Proxy Server in http Accelerator
-Mode|guide::strategy/Adding_a_Proxy_Server_in_http_Ac>.
+Mode|guide::strategy/Adding_a_Proxy_Server_in_http_Accelerator_Mode>.
=head1 Upload and Download of Big Files
@@ -5872,7 +5873,7 @@
downloading of big files, you probably want it to be executed on a
plain apache server under mod_cgi (i.e. performing this operation on
the front-end server, if you use L<a dual-server
-setup|guide::scenario/One_Plain_and_One_mod_perl_enabl>.
+setup|guide::scenario/One_Plain_and_One_mod_perl_enabled_Apache_Servers>.
This of course assumes that the script requires none of the
functionality of the mod_perl server, such as custom authentication
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
