server benchmarking util

Soldato
Joined
3 Jan 2003
Posts
3,710
Guys, I am looking for a good but free benchmark util!

any recommendations? currenly using Nuclearus to compare 2 servers.
 
Personally I'd never benchmark servers in general performance, it's just pointless, benchmark them according to what app they're going to run...
 
Pressured to display what though? As bigredshark has said, you need to test the server for the role its going to perform, such as if it was going to be an exchange server, you can install exchange and then simulate SMTP and client usage to see how well it copes.

Benchmark software is designed for the desktop, but can be useful for things such as disk access issues if looking to upgrade.
 
Pressured to display what though? As bigredshark has said, you need to test the server for the role its going to perform, such as if it was going to be an exchange server, you can install exchange and then simulate SMTP and client usage to see how well it copes.

Benchmark software is designed for the desktop, but can be useful for things such as disk access issues if looking to upgrade.

Jetstress is a good test, but it's only applicable to exchange really and it feeds on disk IO. There are some good tests for SQL as well.

You could run prime or something similar to show processor performance and a disk benchmark to show throughput and latency but it's all fairly meaningless without an app in mind.
 
cheers for the reply guys, gonna use SQLIOSim to and compare the results on 2 servers

3yr 2x dual core cpu
2month old 2x quad core cpu

the development guys are complaining the SQL queries are running slower on the new server compared to the old. however they moved the database's from sql 2000 to 2005, so perhaps its a SQL issue!

thanks again
 
Indeed, always best with SQL to have the logs and the db on different arrays where possible, usually the DB on a 15k SAS raid 10 array and the OS/Logs on a Raid 1 array
 
Indeed, always best with SQL to have the logs and the db on different arrays where possible, usually the DB on a 15k SAS raid 10 array and the OS/Logs on a Raid 1 array

It's a good point in really high load systems, I've dumped both on a 6 disk RAID10 (72GB 15k SAS drives) in the past though and it was quick. Still, as you say it is best practice but unless it's really high load it probably isn't the performance bottleneck...
 
the development guys are complaining the SQL queries are running slower on the new server compared to the old. however they moved the database's from sql 2000 to 2005, so perhaps its a SQL issue!
Have a look at The SQL Performance Dashboard it should let you identify the queries with issues and see if the problems are I/O or CPU bound. It could be as easy as a missing index when you changed servers.

If you get the wait statistics for same application on the old and new server, you should be able to prove your point. Real world information beats benchmarks everytime.

[edit]ok now I'm kicking myself.... I forgot SQL 2000 can't run the performance dashboard. however it should still help you debug your performance problems.[/edit]

akakjs
 
Last edited:
Back
Top Bottom