• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Test your CPU processing power

mdchesne

Banned
mdchesne was working on a simple java program for one of his programming classes when he realized he just made a process-power test. mdchesne exclaimed "woot!"

mdchesne lists the code below (mdchesne removed to save space, available with PM) for your convienence and to show you he included no spyware/harvesters/etc. He made the program to test how long different sorts would take to sort 10,000 times on a 100,000-sized array of randomly-generated numbers. He warns you
unless you have a decent processor, it may take hours ;P

java stress test 100,000 size array sorted 10,000 times
java stress test (extreme edition) 500,00 size array sorted 100,000 times)
mdchesne says the time it takes to sort gets printed in the console (unix or linux) or in the console
winow in windows (be sure to "press any key" to keep window up...it flashes quickly)


mdchesne asks you to
post your timings when you complete the run


mdchesne's screencap running at 80000, halfway through test, working up to 100000
mdchesne's excel documentation with array sizes+timings. graphs on following sheets

========================
Fastest Timing Thus Far
mdchesne @ 11.0766 | 26.2812 | 6.6000 | 2.4922
glugglug @ 8.3531 | 35.3188 | 1.8563 | ??
 
mdchesne says to do the following:

1) open eclipse, run program, look at console window
2) post your timings

1) open *nix terminal and run program, look in console window
2) post your timings
 
Uhm - Armitage thinks it's cool making fast code. Armitage thinks making slow code is easy - even easier in java 😛
 
I'm afraid to try it on my Sempron 2800+ (Socket A). However, I may get my dual Opterons up and running this week, I may try it out then.
 
Originally posted by: ElFenix
ElFenix thinks posting in the third person is lame

Leper Messiah thinks that ElFenix has included himself in the lameness by posting in the third person. But thats just Leper Messiah's opinion.
 
Originally posted by: Leper Messiah
Originally posted by: ElFenix
ElFenix thinks posting in the third person is lame

Leper Messiah thinks that ElFenix has included himself in the lameness by posting in the third person. But thats just Leper Messiah's opinion.

ElFenix thinks this is going to start a neffing trend
 
Originally posted by: ElFenix
Originally posted by: Leper Messiah
Originally posted by: ElFenix
ElFenix thinks posting in the third person is lame

Leper Messiah thinks that ElFenix has included himself in the lameness by posting in the third person. But thats just Leper Messiah's opinion.

ElFenix thinks this is going to start a neffing trend

Armitage think IBL 😀
 
Quick Sort timing: 0.0
Heap Sort timing: 0.16
Merge Sort timing: 0.0
Insertion Sort timing: 0.0

It didn't crash my computer.
 
Originally posted by: sigs3gv
Quick Sort timing: 0.0
Heap Sort timing: 0.16
Merge Sort timing: 0.0
Insertion Sort timing: 0.0

It didn't crash my computer.

mdchesne is sorry, he uploaded the wrong one. he laughs out loud
 
Originally posted by: mdchesne
mdchesne says to expect the following:

1) open crl-alt-del and watch your Performance tab
2) in Eclipse, it will print out the time it took to sort a 100,000 size array 10,000 times
in unix or linux, the console will print it out
3) if your computer crashes, it's normal (mdchesne's friend's athlon XP 3200+ crashed after 5 minutes)


Armitage says this should be in your mdchesne's first post. Armitage would flog you with CAT5 if you crashed Armitage's computer.
 
Originally posted by: Armitage
Originally posted by: mdchesne
mdchesne says to expect the following:

1) open crl-alt-del and watch your Performance tab
2) in Eclipse, it will print out the time it took to sort a 100,000 size array 10,000 times
in unix or linux, the console will print it out
3) if your computer crashes, it's normal (mdchesne's friend's athlon XP 3200+ crashed after 5 minutes)


Armitage says this should be in your mdchesne's first post. Armitage would flog you with CAT5 if you crashed Armitage's computer.

mdchesne laughs out loud
mdchesne explains that one of a few things will happen (as tested by his friend and his xp 3200+:
1) CPU overheat causing shutdown
2) CPU error where the system GUI reverts back to origional settings (basic gray tray, default background, etc)
3) completion
4) error in java file where java loses track of sorting and results in error.
5) forced shutdown of all other programs in an attempt to gain needed processing power
 
Originally posted by: mdchesne
Originally posted by: Armitage
Originally posted by: mdchesne
mdchesne says to expect the following:

1) open crl-alt-del and watch your Performance tab
2) in Eclipse, it will print out the time it took to sort a 100,000 size array 10,000 times
in unix or linux, the console will print it out
3) if your computer crashes, it's normal (mdchesne's friend's athlon XP 3200+ crashed after 5 minutes)


Armitage says this should be in your mdchesne's first post. Armitage would flog you with CAT5 if you crashed Armitage's computer.

mdchesne laughs out loud
mdchesne explains that one of a few things will happen:
1) CPU overheat causing shutdown
2) CPU error where the system GUI reverts back to origional settings (basic gray tray, default background, etc)
3) completion
4) error in java file where java loses track of sorting and results in error.
5) forced shutdown of all other programs in an attempt to gain needed processing power
mdchesne experienced all at one point or another during his testing

Armitage's computer doesn't overheat. Armitage thinks mdchesne's code is a memory pig and the OOM killer is running rampant upon mdchesne's /proc
 
mdchesne assures you it takes 8mbs memory to run java file. TOPS. It runs off CPU only. mdchesne says to look at system processes and performance tabls in task manager for proof
 
mdchesne has just completed all the timings from array sizes 0-10,000 with size(500) increments and 0-100,000 with size(10,000) increments
My timings: 11.0766 | 26.2812 | 6.6 | 2.4922
 
Back
Top