HttPerf - Revision history

Egge at 06:22, 12 October 2009

2009-10-12T06:22:49Z

← Older revision		Revision as of 06:22, 12 October 2009
Line 99:		Line 99:
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:Cygwin]]		[[Category:Cygwin]]
			[[Category:Performance]]

Egge at 13:25, 15 July 2009

2009-07-15T13:25:43Z

← Older revision		Revision as of 13:25, 15 July 2009
Line 92:		Line 92:
	Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0		Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0
	</geshi>		</geshi>

			== Other tests ==

			While there are some pay sites which will do stress tests, and you can do your own with EC2, you can get some good metrics from [http://tools.pingdom.com/?url=http://www.theeggeadventure.com/wikimedia/index.php/HttPerf&treeview=0&column=objectID&order=1&type=0&save=true Pingdom.com] and [http://browsershots.org/http://www.theeggeadventure.com/wikimedia/index.php/Cygwin_Tips Browsershots.org]. Browsershots is quite neat because a whole bunch of different browser will hit your site. You don't have control or metrics, but it's a pretty good gauge of what web users will see.

	[[Category:Linux]]		[[Category:Linux]]
	[[Category:Cygwin]]		[[Category:Cygwin]]

Brianegge at 05:03, 15 July 2009

2009-07-15T05:03:03Z

@@ Line 59: / Line 59: @@
 <geshi lang="bash">
 httperf: connection failed with unexpected error 106
 </geshi>
 [[Category:Linux]]
 [[Category:Cygwin]]

Brianegge: /* Cgywin */

2009-07-15T04:59:28Z

Cgywin

← Older revision		Revision as of 04:59, 15 July 2009
Line 51:		Line 51:
	</geshi>		</geshi>

	== ~~Cgywin~~ ==		== Cygwin ==

	Httperf works great from Cygwin. It's not a standard package, but it's easy to build from source. The usual ./configure && make && make install works fine.		Httperf works great from Cygwin. It's not a standard package, but it's easy to build from source. The usual ./configure && make && make install works fine.

Egge at 02:40, 6 November 2008

2008-11-06T02:40:32Z

← Older revision		Revision as of 02:40, 6 November 2008
Line 1:		Line 1:
	First, compile httperf for your platform. It works just fine under 32 or 64 bit. Use '''file''' to verify the binary matches your platform.		First, compile [http://linux.die.net/man/1/httperf httperf] for your platform. It works just fine under 32 or 64 bit. Use '''file''' to verify the binary matches your platform.
	<geshi lang="bash">		<geshi lang="bash">
	$ file /home/ec2/bin/httperf		$ file /home/ec2/bin/httperf

Egge at 02:39, 6 November 2008

2008-11-06T02:39:44Z

← Older revision		Revision as of 02:39, 6 November 2008
Line 49:		Line 49:
	Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0		Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
	Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0		Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0
			</geshi>

			== Cgywin ==

			Httperf works great from Cygwin. It's not a standard package, but it's easy to build from source. The usual ./configure && make && make install works fine.

			The only caveat is that you can't use the '--hog' option. This option allows httperf to use non ephemeral ports (in the range from 1024 to 5000). If you use the --hog option, you may get this error:

			<geshi lang="bash">
			httperf: connection failed with unexpected error 106
	</geshi>		</geshi>

	[[Category:Linux]]		[[Category:Linux]]
			[[Category:Cygwin]]

Egge at 23:11, 10 September 2008

2008-09-10T23:11:29Z

← Older revision		Revision as of 23:11, 10 September 2008
Line 50:		Line 50:
	Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0		Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0
	</geshi>		</geshi>

			[[Category:Linux]]

Egge: HttpPerf moved to HttPerf

2008-09-10T23:10:58Z

HttpPerf moved to HttPerf

← Older revision		Revision as of 23:10, 10 September 2008
(No difference)

Egge: Httpref moved to HttpPerf: Misspelled

2008-09-10T23:10:00Z

Httpref moved to HttpPerf: Misspelled

← Older revision		Revision as of 23:10, 10 September 2008
(No difference)

Egge at 21:45, 9 March 2008

2008-03-09T21:45:34Z

← Older revision		Revision as of 21:45, 9 March 2008
Line 1:		Line 1:
			First, compile httperf for your platform. It works just fine under 32 or 64 bit. Use '''file''' to verify the binary matches your platform.
			<geshi lang="bash">
			$ file /home/ec2/bin/httperf
			/home/ec2/bin/httperf: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
			$ file /usr/local/bin/httperf
			/usr/local/bin/httperf: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped
			</geshi>

			You'll want ssl compiled in. You can either check to see if the '--ssl' option is available in help, or better yet, check to see if the executable links to the ssl libaries. In Ubuntu I had to make sure I had 'libc6', 'libssl0.9.8', and 'libssl-dev' installed before compiling.

			<geshi lang="bash">
			$ ldd /usr/local/bin/httperf
			libresolv.so.2 => /lib/libresolv.so.2 (0x00002b3181afe000)
			libnsl.so.1 => /lib/libnsl.so.1 (0x00002b3181d13000)
			libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00002b3181f2c000)
			libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x00002b3182175000)
			libm.so.6 => /lib/libm.so.6 (0x00002b31824f7000)
			libc.so.6 => /lib/libc.so.6 (0x00002b3182778000)
			libdl.so.2 => /lib/libdl.so.2 (0x00002b3182ad3000)
			libz.so.1 => /usr/lib/libz.so.1 (0x00002b3182cd8000)
			/lib64/ld-linux-x86-64.so.2 (0x00002b31818e0000)
			</geshi>

			I ran a quick test against Amazon to get an idea of the capacity of my client machine. Looks like I can sustain about 45 conn/s and 455 req/s.
	<geshi lang="bash">		<geshi lang="bash">
	$ httperf --timeout=5 --client=0/1 --server=www.amazon.com --port=443 --uri=/favicon.ico --rate=60 --send-buffer=4096 \		$ httperf --timeout=5 --client=0/1 --server=www.amazon.com --port=443 --uri=/favicon.ico --rate=60 --send-buffer=4096 \