Network stress testing is taken for granted sometimes however it is extremely useful in many aspects of a network. Typically when someone is thinking of stress testing something technology related they are thinking of stress testing a web application of some sort however it is beneficial to also stress test every piece of network hardware from the firewall to the web server that the application is running on to make sure there are no weaknesses once packets touch your network. With that said there are some great applications within Backtrack that provide stress testing capabilities such as siege which is classified as a HTTP/HTTPS Stress Tester which depending on the location you test from could also test network hardware between the Internet and the web server running the application being tested..siegerc, apache, backtrack, HTTP, HTTPS, network stress testing, post, response time, siege, siege.log, stress test, stress testing, transactions, urls.txt, verbose, web server
Posts Tagged “transactions”
Apr 04 2012
When pgbench results are provided they are shown as TPS or transactions per second.
Below is an example of pgbench being used.
bash-3.1$ pgbench -Upostgres -s 10 -c 10 -t 3000 pgbench starting vacuum...end. transaction type: TPC-B (sort of) scaling factor: 1 number of clients: 10 number of transactions per client: 3000 number of transactions actually processed: 30000/30000 tps = 251.358621 (including connections establishing) tps = 251.468863 (excluding connections establishing)
In the above example the transactions per second averages 251.Tags: benchmark, pgbench, postgres, PostgreSQL, tps, transactions