Overclocking on UNIX

[ErNciLator]

Are there any tools, like SuperPi or Prime or anything that I could use in a UNIX environment to test stability? (FreeBSD)

 

[Craig321]

http://www.mersenne.org/freesoft.htm

Unix and non-x86 users should check out Ernst Mayer's Mlucas page and the Glucas page for guidance as to which code is best for their platform.

 

[ErNciLator]

Thanks and more?

 

[BillytheImpaler]

The oldest and perhaps best benchmark for a Unix-like system is compiling the kernel. I'm more familiar with Linux than FreeBSD but I imagine the following is relevant to you. As long as you use the same config file, this will give you a pretty good idea of how you're computer is scaling as you overclock. It will also give you an idea of stability because an unstable system will cause compilation errors. You will need to keep your own log of compile times for reference. This can be used to compare separate systems as long as the same architecture and config file are used. To time your source compile, simply enter the kernel source directory (i.e. /usr/src/linux/) and type

# time make

when it is done, it will display the overall time it took to complete, which you can then throw in to a text document or spreadsheet to graph, if you'd like.

This is where I stole that from: http://www.ocforums.com/showthread.php?t=486495

There are other helpful tools there too.

 

[Craig321]

The oldest and perhaps best benchmark for a Unix-like system is compiling the kernel. I'm more familiar with Linux than FreeBSD but I imagine the following is relevant to you. As long as you use the same config file, this will give you a pretty good idea of how you're computer is scaling as you overclock. It will also give you an idea of stability because an unstable system will cause compilation errors. You will need to keep your own log of compile times for reference. This can be used to compare separate systems as long as the same architecture and config file are used. To time your source compile, simply enter the kernel source directory (i.e. /usr/src/linux/) and type

# time make

when it is done, it will display the overall time it took to complete, which you can then throw in to a text document or spreadsheet to graph, if you'd like.

This is where I stole that from: http://www.ocforums.com/showthread.php?t=486495

There are other helpful tools there too.

The problem with that way is it won't tell you any e.g. memory errors, will it??

EDIT

I take that back, it says it'll tell you about errors.

Thanks and more?

Go to that link I gave, at the top it says something about Unix and provides 2 further links, there should be information and instructions there.