Jump to content
HWBOT Community Forums

hwbotprime on PS3 with Linux


moog

Recommended Posts

Hello, I've decided to run hwbotprime on a PS3 running Debian Linux. It went okay, but there are a couple caveats.

 

First, 0.8.3 is broken on big-endian. Not sure how this may affect results, but it's pretty serious if we're missing primes because numbers are read backwards.

Secondly, it fails to detect the CPU clock and name.

Thirdly, the results vary significantly between running the test in CLI (316.88ps) and GUI (240-280ps).

 

mdec@Tycho:~/hwbot$ java -jar hwbotprime-0.8.3.jar 
OpenJDK Zero VM warning: You have loaded library /tmp/libCpuId-32-0.8.3.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
Failed to load native library CpuId-32-0.8.3 on OS linux: /tmp/libCpuId-32-0.8.3.so: /tmp/libCpuId-32-0.8.3.so: kodowanie danych w pliku ELF nie jest big-endian (Possible cause: endianness mismatch)
--------- HWBOT Prime 0.8.3 ----------

Processor detected:

Estimating speed... 2x n/aMHz
211 MB memory
Running benchmark using 2 threads.
Starting benchmark...
Warm up phase:   ..................................................................................................... done!
Benchmark phase: ..................................................................................................... done!
All done!
Score: 316.88.
Hit enter to compare online, enter a filename to save to file, or type q to quit.
ps3-results
q
Saved file: ps3-results.hwbot
Hit enter to compare online, enter a filename to save to file, or type q to quit.
Bye!

Here's what /proc/cpuinfo has to say about CPU detection:

mdec@Tycho:~$ cat /proc/cpuinfo
processor       : 0
cpu             : Cell Broadband Engine, altivec supported
clock           : 3192.000000MHz
revision        : 5.1 (pvr 0070 0501)

processor       : 1
cpu             : Cell Broadband Engine, altivec supported
clock           : 3192.000000MHz
revision        : 5.1 (pvr 0070 0501)

timebase        : 79800000
platform        : PS3
model           : SonyPS3

And here's a screenshot:

z247EYf.png

Additional info: kernel 3.15.10, IcedTea 2.6.4 (7u95-2.6.4-1~deb7u1)

Link to comment
Share on other sites

  • Crew

Thirdly, the results vary significantly between running the test in CLI (316.88ps) and GUI (240-280ps).

 

I see the same for Raspberry Pi subs: Niuulh`s HWBOT Prime score: 2138.68 pps with a Broadcom BCM2836 (BCM2709)

 

The GUI is a major performance drawback and makes the benchmark inconsistent.

 

Edit: Screenshot function is not working on Linux. So this is another bug.

Edited by Strunkenbold
Link to comment
Share on other sites

Link?

[Tutorial] How to Install and run Linux on your PS4 - via WOLOLO

How to Install and run Linux on your PS4 - Wololo.net

https://www.reddit.com/r/linux/comments/3yt1dl/linux_on_the_ps4/

I think thats the part where he said hwbot prime is broken on big endian...

 

 

@Massman I will try to create an entry...

 

EDIT: Sony Playstation 3 @ HWBOT

Big thanks! :D I've already added a result.

Hard to tell if this is good or bad, but it's pretty awesome to see :)

 

The code of HWBOT prime is open source, in case you want to add code to optimize for the PS3 https://github.com/frederikcolardyn/hwbotprime

@Strunkenbold: do we have database support for this? :D

I will definitely try to see if any optimizations can be made :) There's plenty of possibilities. Since this is Java, we're probably getting only PPE results. Right off the top of my head I can think of 3 things that require attention: endianess, AltiVec utilization and SPE execution. As soon as I take a look at the code when I'm back at home, I will confirm the most obvious disaster scenario - that the endianess mismatch causes the test to give false positives and false negatives.

 

I've also noticed that HWBOT has an OpenGL test. This can also be run on the PS3 under Linux, but it won't test the GPU until Linux has a DRM driver for the RSX and Mesa has a GL implementation for RSX. If you get an older version of Mesa (8-10) you can compile a very incomplete implementation of GL for SPE, which is still pretty slow and throws artifacts around like crazy. It got removed in newer releases because its development ceased. If you're going with stock Mesa, you're still testing just the PPE.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...