Lightweight Performance Testing with PowerShell

re: Lightweight Performance Testing with PowerShell

BP — Tue, 29 Jan 2008 09:50:15 GMT

This post reminds me of Eric Lipperts comment:

"I've said before that we designed the script languages to make it easy to quickly write simple scripts to automate web page functionality, choose what HTML to serve up in ASP, or write better batch files, but that they were explicitly not designed to be fully-fledged high-performance production languages for solving really complex or data-intensive problems. "

Link to his full post: http://blogs.msdn.com/ericlippert/archive/2003/11/18/53388.aspx

» Daily Bits - January 29, 2008 Alvin Ashcraft’s Daily Geek Bits: Daily links, development, gadgets and raising rugrats.

Tue, 29 Jan 2008 15:34:46 GMT

PingBack from http://www.alvinashcraft.com/2008/01/29/daily-bits-january-29-2008/

re: Lightweight Performance Testing with PowerShell

marco.shaw — Wed, 30 Jan 2008 05:57:12 GMT

This reminds me of a couple of PowerShell scripts written to solve a Sudoku puzzle... One method took over 24 hours, another took 22 seconds.

re: Lightweight Performance Testing with PowerShell

Vinicius Canto [MVP] — Sun, 10 Feb 2008 06:20:42 GMT

Hi,

I have one tip for who wants to use PowerShell to make some performance tests: choose N (where N is the number of tests) carefully. A wrong N number could result in a wrong conclusion...

http://en.wikipedia.org/wiki/Confidence_interval

[]s,

Vinicius Canto

MVP Windows Server - Admin Frameworks

Brazil