By: sathish

sathish — Mon, 21 Jan 2013 06:36:42 +0000

Its really good information.

By: Arpit

Arpit — Tue, 29 Mar 2011 09:20:15 +0000

You also need to remove human interaction in a benchmark, this gets you reliable results. i.e: do not get input from the keyboard, but from file.

http://www.indianhostinginfo.com/search/label/Linux%20Tutorial

By: TheLinuxBlog.com

TheLinuxBlog.com — Mon, 24 Jan 2011 15:10:08 +0000

Great tips!

By: georges

georges — Mon, 24 Jan 2011 15:08:05 +0000

Thanks for that post!
Another thing I’ve done before in optimizing code, is use an analyzer that tells me which part of the code represents the most time.
Often you find that 80% of the time is spent on 20% of the code.
Then you focus on optimizing that part of the code. When you’re done optimizing that, redo the analysis, and again focus on the top routine.

For C language, the tools were called pixie and prof. Don’t know the equivalents in shell languages though.

You also need to remove human interaction in a benchmark, this gets you reliable results. i.e: do not get input from the keyboard, but from a text file.

Also, you need to get a reference output result. Then after each run, compare your output to the reference one. If the outputs match, then you can compare times and make decisions. Otherwise, fix the bug you just introduced, and start again

Comments on: Optimizing Shell Scripts

By: sathish

By: Arpit

By: TheLinuxBlog.com

By: georges