<?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: Apche build help in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215903#M893661</link>
    <description>I maintain a small Free (OpenSource) project.  We regularly release new files that are quite large.  &lt;BR /&gt;We have a Intel server running Red Hat Linux and the Apache httpd that's included in that distro, which is a full blown webserver.&lt;BR /&gt;At release times, the box would get bogged down and almost buckle under the pressure from people downloading.  So we investigated.&lt;BR /&gt;Turned out that it was total folley to use such a full blown httpd for a simple file transfer.&lt;BR /&gt;&lt;BR /&gt;I built a very stripped down apache, ran it on another port on the machine and directed downloads to it.  That dramaticly cut down on the load and more people could download at the same time.   Still there where problems.&lt;BR /&gt;So I ended up changing the downloads to use the ftp server (ftp:// urls) and now bandwidth is the limiting factor :)&lt;BR /&gt;</description>
    <pubDate>Tue, 23 Mar 2004 09:06:28 GMT</pubDate>
    <dc:creator>Richard Allen</dc:creator>
    <dc:date>2004-03-23T09:06:28Z</dc:date>
    <item>
      <title>Apche build help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215902#M893660</link>
      <description>Hey all,&lt;BR /&gt;&lt;BR /&gt;I've got an Lclass running Apache 2.x that is maintained by developers for their app. They've requested we add another node that will be used to serve up nothing but images, so we're adding a box to do just that. Here's my dilema. The developers don't want to change how they build their Apache. At the moment it's build static w/ mpm prefork, mod_ssl and a handfull of other modules. I'm trying to persuade them that we might see better performance from this "image" server if we trim the fat from Apache and build it with mpm worker to make it fully threaded.&lt;BR /&gt;&lt;BR /&gt;Wouldn't it be better for performance if we build Apache to use dymanic modules and with mpm worker? After all, it's only purpose will be to server up images and will be secure... &lt;BR /&gt;&lt;BR /&gt;What type of metrics should be used to compare HP's Apache Build -vs- my developer's build?&lt;BR /&gt;&lt;BR /&gt;Thanks for all the input!&lt;BR /&gt;-denver</description>
      <pubDate>Thu, 11 Mar 2004 07:31:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215902#M893660</guid>
      <dc:creator>Denver Osborn</dc:creator>
      <dc:date>2004-03-11T07:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: Apche build help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215903#M893661</link>
      <description>I maintain a small Free (OpenSource) project.  We regularly release new files that are quite large.  &lt;BR /&gt;We have a Intel server running Red Hat Linux and the Apache httpd that's included in that distro, which is a full blown webserver.&lt;BR /&gt;At release times, the box would get bogged down and almost buckle under the pressure from people downloading.  So we investigated.&lt;BR /&gt;Turned out that it was total folley to use such a full blown httpd for a simple file transfer.&lt;BR /&gt;&lt;BR /&gt;I built a very stripped down apache, ran it on another port on the machine and directed downloads to it.  That dramaticly cut down on the load and more people could download at the same time.   Still there where problems.&lt;BR /&gt;So I ended up changing the downloads to use the ftp server (ftp:// urls) and now bandwidth is the limiting factor :)&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Mar 2004 09:06:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215903#M893661</guid>
      <dc:creator>Richard Allen</dc:creator>
      <dc:date>2004-03-23T09:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Apche build help</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215904#M893662</link>
      <description>There is a lot of fat in apache thats not needed. You should do some performance monitoring with glance or my system.perf.sh scripts once you have your build.&lt;BR /&gt;&lt;BR /&gt;I'd watch cpu,shared memory use and networking.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 23 Mar 2004 10:10:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apche-build-help/m-p/3215904#M893662</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-03-23T10:10:26Z</dc:date>
    </item>
  </channel>
</rss>

