<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Apache: How to improve performance on OpenVMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5348451#M45591</link>
    <description>&lt;P&gt;Yes, agree with this, we implemented these changes 3 or 4 years ago and have had no problems since.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Login does as little as possible:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;$ ! Login.Com for Apache HTTP (WWW) Server&lt;/P&gt;&lt;P&gt;$ !&lt;/P&gt;&lt;P&gt;$ set proc/parse=extend&lt;/P&gt;&lt;P&gt;$ exit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Overnight during low/no web site usage time:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;$ pu apache_disk:[apache.specific.*]&lt;/P&gt;&lt;P&gt;$ ren/exc=*.dir apache_disk:[apache.specific.*]*.* ;1&lt;/P&gt;</description>
    <pubDate>Thu, 29 Sep 2011 13:40:18 GMT</pubDate>
    <dc:creator>Peter Barkas</dc:creator>
    <dc:date>2011-09-29T13:40:18Z</dc:date>
    <item>
      <title>Apache: How to improve performance on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5347339#M45590</link>
      <description>&lt;P&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;After analyzing serious performance problems with Apache CSWS V2.2 on a fairly busy BL860C i2 OpenVMS 8.4 system, I've come to the following conclusions that might benefit others:&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;1. When file version numbers on log files in apache$specific:[000000] get to ;32767, the following entries will be seen in the system accounting file:&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;LOGIN FAILURE&lt;BR /&gt;-------------&lt;BR /&gt;Username:          APACHE$WWW &lt;BR /&gt;...&lt;BR /&gt;Final status text: %&lt;STRONG&gt;&lt;FONT size="1"&gt;RMS-E-CRE, ACP file create failed&lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;...&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;When this occurs, there are significant delays when web clients load pages from the Apache server.&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;After using a utility to reset the version numbers on these log files, performance is restored. The difference was dramatic.&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;2. If there's the DCL command "SET DIRECTORY/VERSION_LIMIT=10" in apache$common:[000000]login.com, which may be there if you've upgraded from previous CSWS versions, the following entry is seen in the system accounting log:&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;LOGIN FAILURE&lt;BR /&gt;-------------&lt;BR /&gt;Username:          APACHE$WWW&lt;BR /&gt;...&lt;BR /&gt;Final status text: &lt;STRONG&gt;%RMS-E-FLK, file currently locked by another user&lt;BR /&gt;&lt;/STRONG&gt;...&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="3" face="arial,helvetica,sans-serif"&gt;This also results in delays when loading pages and unnecessary disk I/O. While this condition is not as frequent as the first, the "SET DIRECTORY/VERSION_LIMIT=10" command should be removed from login.com. I suspect you'll only have this command if you've upgraded from previous versions of CSWS.&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2011 20:18:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5347339#M45590</guid>
      <dc:creator>Carl Karcher</dc:creator>
      <dc:date>2011-09-28T20:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: Apache: How to improve performance on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5348451#M45591</link>
      <description>&lt;P&gt;Yes, agree with this, we implemented these changes 3 or 4 years ago and have had no problems since.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Login does as little as possible:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;$ ! Login.Com for Apache HTTP (WWW) Server&lt;/P&gt;&lt;P&gt;$ !&lt;/P&gt;&lt;P&gt;$ set proc/parse=extend&lt;/P&gt;&lt;P&gt;$ exit&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Overnight during low/no web site usage time:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;$ pu apache_disk:[apache.specific.*]&lt;/P&gt;&lt;P&gt;$ ren/exc=*.dir apache_disk:[apache.specific.*]*.* ;1&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2011 13:40:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5348451#M45591</guid>
      <dc:creator>Peter Barkas</dc:creator>
      <dc:date>2011-09-29T13:40:18Z</dc:date>
    </item>
    <item>
      <title>Re: Apache: How to improve performance on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5363647#M45592</link>
      <description>&lt;P&gt;Best way to improve webserver performance on OpenVMS is to run WASD instead of Apache! :-)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Seriously, WASD is much more efficient and doesn't insist that every file being served is StreamLF. It also doesn't create thousands of log files unless you want it to.)&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2011 07:17:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5363647#M45592</guid>
      <dc:creator>Jeremy Begg</dc:creator>
      <dc:date>2011-10-17T07:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: Apache: How to improve performance on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5415767#M45593</link>
      <description>Doubled. I have found great impreovements on my (small-memory) VMS webserver by simply chnaging from Apache to WASD, Apart from that: WASD comes with a TREMENDOUSLY helpfool toolkit - buitlt-in.</description>
      <pubDate>Mon, 12 Dec 2011 20:59:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/apache-how-to-improve-performance-on-openvms/m-p/5415767#M45593</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2011-12-12T20:59:54Z</dc:date>
    </item>
  </channel>
</rss>

