Stress Testing an Apache Application Server in a Real World Environment
- « first
- ‹ previous
- 1
- 2
- 3
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- Designing Electronics with Linux
- What's the tweeting protocol?
- Kernel Problem
2 hours 30 min ago - BASH script to log IPs on public web server
6 hours 58 min ago - DynDNS
10 hours 33 min ago - Reply to comment | Linux Journal
11 hours 6 min ago - All the articles you talked
13 hours 29 min ago - All the articles you talked
13 hours 32 min ago - All the articles you talked
13 hours 34 min ago - myip
17 hours 58 min ago - Keeping track of IP address
19 hours 49 min ago - Roll your own dynamic dns
1 day 1 hour ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
./flood configuration-file
./flood configuration-file *gt; output.file
That sikiş should have been > which would have given >, i.e.:
./flood configuration-file > output.file
Re: Stress Testing an Apache Application Server in a Real World
please, i'm cannot run this command:
/usr/lib/sa/sadc 1 [# of seconds to report] outfile
where can i get sadc, please anybody ..
tq
Re: Stress Testing an Apache Application Server in a Real World
You can get the links for download at the authors site http://perso.wanadoo.fr/sebastien.godard/
Re: Stress Testing an Apache Application Server in a Real World
i'm cannot ru this command
/usr/lib/sa/sadc 1 [# of seconds to report] outfile
when can i get sadc? please help me
Re: Stress Testing an Apache Application Server in a Real World
Hi,
I'm trying to GET an URL protect by user&password and I don't find any info about syntax I needed. I try to simulate a direct telnet to a web server but it doesn't work:
telnet [host] 80
GET http://host/index.html HTTP/1.1
Authorization: Basic [code]
Host: [host]
Any idea.
Thank's.
Re: Stress Testing an Apache Application Server in a Real World
If its standard Basic auth that we're talking about then, the authorization header is just the username and password concatenated together and then base64 encoded so
perl -MMIME::Base64 -e 'print encode_base64("Aladdin:open sesame") . "
";'
will print the value QWxhZGRpbjpvcGVuIHNlc2FtZQ== which you would then put in your authorization header:
telnet [host] 80
GET /protected_document.html HTTP/1.0
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
[server response should come here]
Re: Stress Testing an Apache Application Server in a Real World
Thank you for your answer, but maybe I'm not express very good.
I want the flood XML syntax to simulate this commands; so, how to pass user and password information in stress testing.
Thanks.
Typo
./flood configuration-file *gt; output.file
That should have been > which would have given >, i.e.:
./flood configuration-file > output.file
Re: Typo
I guess you meant
"That should have been > which would have given > ..."
Isn't not previewing a *****? ;-)
you mean: this should be
you mean:
this should be > which would > ...