Code: Select all
pi@raspberrypi2:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 57.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 1
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 57.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 2
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 57.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
processor : 3
model name : ARMv7 Processor rev 5 (v7l)
BogoMIPS : 57.60
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 5
Hardware : BCM2709
Revision : a01041
Serial : 000000003fdd6efYou can overclock the pi3. It will easily run at 1.3 GHz.DavidTheDolphin wrote:Bonjour,
J'ai lu des comparatifs sur les différences de perfs entre le Pi 2 et le Pi 3 à leurs fréquences nominales hors j'ai lu aussi qu'il n'était pas permis d'OC le Pi3 alors que mes Pi 2 tournent à 1.1 ghz...
Quelqu'un aurait des infos sur les différences entr'un Pi 2 OC et un Pi 3 SVP ?
Merci,
A+
David
Merci mais je doute qu'il s'agisse d'un comparatif entr'un Pi3 et un Pi2 OC à 1.1ghz.JumpZero wrote:C'est surtout un nouveau SoC! Pour les perfs voir ici https://www.raspberrypi.org/magpi/raspb ... enchmarks/
Since when? That is news to me. (but even if that is true, it is just $35 in any event....which is a tank of petrol/gas)DavidTheDolphin wrote:Thank you for your answer but this kind of OC will void waranty
Show me where overclocking the pi3 voids warranty. Just because there are no raspi-config overclock presets, doesn't mean overclocking isn't supported, or that doing so voids manufacturer warranty.DavidTheDolphin wrote:Pi 3 doesn't officially support overclocking.
No, overclocking doesn't void the warantyDavidTheDolphin wrote:Thank you for your answer but this kind of OC will void waranty
Can the Pi 3 be overclocked?
Overclocking the Raspberry Pi 3 is not recommended and you may void your warranty attempting to do so.
DavidTheDolphin wrote:https://www.element14.com/community/doc ... tions-faqs
Can the Pi 3 be overclocked?
Overclocking the Raspberry Pi 3 is not recommended and you may void your warranty attempting to do so.
The answer, again, would still be yes.DavidTheDolphin wrote:Potentialy my boss will pay a lot of Pi 3 so the waranty is important !
My Pi 2 are OC @1.1ghz, the object of my post is to know if a Pi 3 (with his waranty !) has much more perf than Pi 2 @1.1ghz
I have two: Sysbench with validated run, and Linpack bench :DavidTheDolphin wrote:Do you have a benchmark please ?

Code: Select all
sudo apt-get install sysbenchCode: Select all
sysbench --num-threads=4 --test=cpu --cpu-max-prime=20000 --validate run
Code: Select all
pi@raspberrypi:~ $ sysbench --num-threads=4 --test=cpu --cpu-max-prime=20000 --validate run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 4
Additional request validation enabled.
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 119.9360s
total number of events: 10000
total time taken by event execution: 479.6257
per-request statistics:
min: 47.69ms
avg: 47.96ms
max: 168.58ms
approx. 95 percentile: 48.26ms
Threads fairness:
events (avg/stddev): 2500.0000/8.60
execution time (avg/stddev): 119.9064/0.02

Code: Select all
sudo apt-get install libmpich-dev
wget http://web.eece.maine.edu/~vweaver/junk/pi3_hpl.tar.gz
tar -xvzf pi3_hpl.tar.gz
chmod +x xhplCode: Select all
./xhplCode: Select all
pi@raspberrypi:~ $ ./xhpl
================================================================================
HPLinpack 2.1 -- High-Performance Linpack benchmark -- October 26, 2012
Written by A. Petitet and R. Clint Whaley, Innovative Computing Laboratory, UTK
Modified by Piotr Luszczek, Innovative Computing Laboratory, UTK
Modified by Julien Langou, University of Colorado Denver
================================================================================
An explanation of the input/output parameters follows:
T/V : Wall time / encoded variant.
N : The order of the coefficient matrix A.
NB : The partitioning blocking factor.
P : The number of process rows.
Q : The number of process columns.
Time : Time in seconds to solve the linear system.
Gflops : Rate of execution for solving the linear system.
The following parameter values will be used:
N : 8000
NB : 256
PMAP : Row-major process mapping
P : 1
Q : 1
PFACT : Left
NBMIN : 2
NDIV : 2
RFACT : Right
BCAST : 2ring
DEPTH : 0
SWAP : Mix (threshold = 64)
L1 : transposed form
U : transposed form
EQUIL : yes
ALIGN : 8 double precision words
--------------------------------------------------------------------------------
- The matrix A is randomly generated for each test.
- The following scaled residual check will be computed:
||Ax-b||_oo / ( eps * ( || x ||_oo * || A ||_oo + || b ||_oo ) * N )
- The relative machine precision (eps) is taken to be 1.110223e-16
- Computational tests pass if scaled residuals are less than 16.0
================================================================================
T/V N NB P Q Time Gflops
--------------------------------------------------------------------------------
WR02R2L2 8000 256 1 1 55.37 6.166e+00
HPL_pdgesv() start time Sat Apr 23 15:14:17 2016
HPL_pdgesv() end time Sat Apr 23 15:15:12 2016
--------------------------------------------------------------------------------
||Ax-b||_oo/(eps*(||A||_oo*||x||_oo+||b||_oo)*N)= 0.0025941 ...... PASSED
================================================================================
Finished 1 tests with the following results:
1 tests completed and passed residual checks,
0 tests completed and failed residual checks,
0 tests skipped because of illegal input values.
--------------------------------------------------------------------------------
End of Tests.Code: Select all
sysbench --num-threads=4 --test=cpu --cpu-max-prime=20000 --validate run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 4
Additional request validation enabled.
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 20000
Test execution summary:
total time: 177.8687s
total number of events: 10000
total time taken by event execution: 711.3230
per-request statistics:
min: 70.55ms
avg: 71.13ms
max: 201.39ms
approx. 95 percentile: 71.13ms
Threads fairness:
events (avg/stddev): 2500.0000/6.04
execution time (avg/stddev): 177.8308/0.02
DavidTheDolphin wrote:
Linpack benchmark (N=8000) : ~ vs 6.16 Gflops
How long may I wait ???
Sounds like a crash (which basically means your pi2 spectacularly failed the benchmark, and is in a nutshell incapable/or borderline incapable of running the benchmark as configured....usually as a result of unstable overclocking, voltage/power issues, or cooling issues)...See if you can do anything on the pi2, if it is locked up/frozen, you may need to reboot/restart.DavidTheDolphin wrote:OK :/
I'm in an SSH console so i have no clock to look at... But I've been waiting for 90 minutes now !
Instead of trying to raise voltage, lower the arm_freq...that is probably what is wrong. 1.1 GHZ is likely unstable.DavidTheDolphin wrote:OK, new try with a little more CPU voltage (1.35V instead of 1.3) :
First attempt --> segmentation fault (core dumped)
Second attempt --> freeze again
Higher voltage will set waranty bit...
In "normal" conditions @1.1ghz/1.3V I add no freeze until this bench