- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Apche build help
Operating System - HP-UX
1748272
Members
4290
Online
108760
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2004 11:31 PM
тАО03-10-2004 11:31 PM
Apche build help
Hey all,
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.
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...
What type of metrics should be used to compare HP's Apache Build -vs- my developer's build?
Thanks for all the input!
-denver
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.
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...
What type of metrics should be used to compare HP's Apache Build -vs- my developer's build?
Thanks for all the input!
-denver
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2004 01:06 AM
тАО03-23-2004 01:06 AM
Re: Apche build help
I maintain a small Free (OpenSource) project. We regularly release new files that are quite large.
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.
At release times, the box would get bogged down and almost buckle under the pressure from people downloading. So we investigated.
Turned out that it was total folley to use such a full blown httpd for a simple file transfer.
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.
So I ended up changing the downloads to use the ftp server (ftp:// urls) and now bandwidth is the limiting factor :)
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.
At release times, the box would get bogged down and almost buckle under the pressure from people downloading. So we investigated.
Turned out that it was total folley to use such a full blown httpd for a simple file transfer.
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.
So I ended up changing the downloads to use the ftp server (ftp:// urls) and now bandwidth is the limiting factor :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2004 02:10 AM
тАО03-23-2004 02:10 AM
Re: Apche build help
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.
I'd watch cpu,shared memory use and networking.
SEP
I'd watch cpu,shared memory use and networking.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP