GreeneComputing » Linpack

KISS

Nacoma — Tue, 10 Aug 2010 20:44:19 +0000

I try to follow the KISS principle… Keep It Simple Stupid.
I haven’t updated Linpack in a long time and I knew that I need to make some major changes. So, I updated the app this morning with the first major change in almost 4 months. I increased the matrix that is calculated from 200×200 to 500×500. This change was done to hopefully reduce the number of erroneous MFLOPS numbers. With the matrix at 200, times were starting to get well under 1 second. This is not good for a timing benchmark. Since FroYo is taking over, the matrix had to be
enlarged to make the calculation take longer. This happened with the Java Linpack in the 90s, with faster systems they had to increase the size of the matrix too.

Don’t be surprised if your Linpack run takes up to 6 times longer to run, it’s supposed to do that. Look at the resulting MFLOPS over several runs; hopefully they will be more consistent.

I also updated the Mhz value obtained to show the actual Mhz the system is running at the end of the Linpack run. And I included a new button for the Latest Runs. This shows the latest runs by everyone (slow or fast) over the last few days.

Nexus One with Froyo takes the Lead at 40.099 MFLOPS

Nacoma — Tue, 16 Mar 2010 02:31:21 +0000

We’ve had two different Nexus One phones with four good Top 10 Linpack runs. The best being 40.099 MFLOPS! Looks like some Droids need to do some catching up. I’m fairly certain that these are not bogus runs, since I’ve added some anti-cheat mechanisms to the most recent release. Still some funny results do occur when you overclock.

So is it Google teasing us??

As cyanogen said via twitter “Linpack #4 is an N1 running Froyo. Cheaters”

And of course, TheDudesAndroid said “***shakes fist at userid****”

XDAndroid

Nacoma — Sat, 13 Mar 2010 04:12:13 +0000

TMONEWS has a posting about XDAndroid and how it is much more stable on a HTC Touch Pro 2. As they state, “the Android installation experiences no difficulty in making calls, sending SMS, downloading apps, or browsing the web. In fact, pretty much everything works besides GPS, Bluetooth, and the camera. ”

XDAndroid is a project to port Android to Windows Mobile devices. This is being developed by the guys on the forums of xda-developers.

What I found interesting was that there were a couple Linpack postings for XDAndroid loaded devices. So, I added XDANDROID to the Device list. It will be interesting to see how well it performs on Windows Mobile devices.

Removed Jw52637 50.592 Run from TOP10

Nacoma — Fri, 12 Mar 2010 04:40:42 +0000

Ok, sorry Jw52637. I decided to delist the 50.592 run from the Top10 list. I’ve received and seen lots of comments from people that the run was faked, that you hacked into the list or I just made it up. From what I can tell it was a legitimate Linpack run since I have a check for fake uploads. I also doubt the site was hacked to add it since it also had the right check value. About the only thing I can think, that it didn’t run correctly and thus had an incorrect MFLOP number. I say this since his runs the day before topped out at 9.269

So in the next version, I’m going to check for an invalid run so that it can’t get uploaded.

Friendly little Linpack War

Nacoma — Sun, 07 Mar 2010 02:46:45 +0000

Taking a few days off from here because of my “real” job was hitting the fan. I see that we have a Linpack War going on. If you look at the Top 10 list and the Nexus One device list you’ll see lots of movement. AndroidSpin has done a nice job of covering all the bases on the reasons behind the friendly competition.
“Originally this was just a “friendly” little bet between WootRoot and TheDudesAndroid that a 2.0GHz kernel would or wouldn’t work on the Nexus One. Somehow WootRoot convinced Kmobs to build the kernel (I have a feeling Chris Soyars also played a part in that) and WootRoot bet TheDudesAndroid $50 that he could boot his Nexus, send a tweet and play a video before his phone melted.

WootRoot tried. It didn’t work. But it also didn’t melt. Kmobs got curious and toyed around with frequencies and voltages and they went from 1.113GHz (which was supposed to be the stable max) to 1.267GHz. Of course, it wasn’t until Acsteffy87 decided to run the kernel on his Nexus as well, that TheDudesAndroid found his “courage” and booted it on his too. (I think I’m going to be in trouble for that, lol.) At first, only The Dude’s Nexus would overclock to 1.267GHz and for that reason, it was dubbed the “JesusPhone” or JP1.”