Overclocking Pi 2 - Printable Version

Overclocking Pi 2 - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166)
+---- Thread: Overclocking Pi 2 (/showthread.php?tid=217170)

Pages: 1 2 3 4 5 6 7 8 9 10 11

RE: Overclocking Pi 2 - Milhouse - 2015-03-05

(2015-03-05, 11:18)twelvebore Wrote: With the stock OE install, I mounted the NFS volume and 'dd'd 800MB of the movie file to /dev/null, it gave me an average speed of 6Mbyte/sec.

If you're playing movies with bit rates up to 70Mbit/s and your network is only capable of 6MBytes/sec, then that's potentially a major problem.

However, the Pi2 is easily capable of saturating the 100Mb/s network link, and it can do this without overclocking:

Code:
rpi22:~ # dd if=/storage/freenas/media/Video/test.mkv of=/dev/null

485332+1 records in

485332+1 records out

248490131 bytes (237.0MB) copied, 22.215919 seconds, 10.7MB/s

So I'd say there's something wrong with your network (router? ethernet cable?) or your NAS/NFS server, because 6MBytes/sec is way too low for a properly configured, wired, network.

Also check how you are mounting your NFS share - using larger rsize/wsize buffers and udp instead of tcp can improve throughput. This is what I have in my autostart.sh for my OS NFS mounts:

Code:
NFSOPTS=nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp

[ ! -d /storage/freenas ] && mkdir /storage/freenas

mount -t nfs 192.168.0.3:/mnt/share /storage/freenas -o $NFSOPTS &

RE: Overclocking Pi 2 - twelvebore - 2015-03-05

(2015-03-05, 13:54)Milhouse Wrote: So I'd say there's something wrong with your network (router? ethernet cable?) or your NAS/NFS server, because 6MBytes/sec is way too low for a properly configured, wired, network.

The NFS server is Windows based (the Hanewin one). To be honest I'd not really paid a lot of attention to the setup of it because, as I say, the NUC connected to the same switch as the Pi can get 21MB/sec and play these movies without a hitch (it's running OE 4.2.1).

I'll do some more tests tonight - the server is a 15-drive RAID so read speed should be several hundred MB/sec from disc, and the NUC should be able to saturate a GbE link.

Quote:Also check how you are mounting your NFS share - using larger rsize/wsize buffers and udp instead of tcp can improve throughput. This is what I have in my autostart.sh for my OS NFS mounts:

Code:
NFSOPTS=nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp [ ! -d /storage/freenas ] && mkdir /storage/freenas mount -t nfs 192.168.0.3:/mnt/share /storage/freenas -o $NFSOPTS &

OK. Daft question - I share my library using MySQL, so all the paths are nfs://192.168.1.222/movies/blahblahblah, and rely on Kodi to do the mount/dismount. Is it possible to change NFS options that Kodi uses when it mounts NFS volumes?

RE: Overclocking Pi 2 - Milhouse - 2015-03-05

(2015-03-05, 14:29)twelvebore Wrote: OK. Daft question - I share my library using MySQL, so all the paths are nfs://192.168.1.222/movies/blahblahblah, and rely on Kodi to do the mount/dismount. Is it possible to change NFS options that Kodi uses when it mounts NFS volumes?

No, not yet, although there has been some discussion to try and bring nfs:// closer to OS mounts in terms of performance.

RE: Overclocking Pi 2 - ikecomp - 2015-03-05

(2015-03-05, 13:54)Milhouse Wrote:
(2015-03-05, 11:18)twelvebore Wrote: With the stock OE install, I mounted the NFS volume and 'dd'd 800MB of the movie file to /dev/null, it gave me an average speed of 6Mbyte/sec.

If you're playing movies with bit rates up to 70Mbit/s and your network is only capable of 6MBytes/sec, then that's potentially a major problem.

However, the Pi2 is easily capable of saturating the 100Mb/s network link, and it can do this without overclocking:

Code:
rpi22:~ # dd if=/storage/freenas/media/Video/test.mkv of=/dev/null 485332+1 records in 485332+1 records out 248490131 bytes (237.0MB) copied, 22.215919 seconds, 10.7MB/s

So I'd say there's something wrong with your network (router? ethernet cable?) or your NAS/NFS server, because 6MBytes/sec is way too low for a properly configured, wired, network.

Also check how you are mounting your NFS share - using larger rsize/wsize buffers and udp instead of tcp can improve throughput. This is what I have in my autostart.sh for my OS NFS mounts:

Code:
NFSOPTS=nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp [ ! -d /storage/freenas ] && mkdir /storage/freenas mount -t nfs 192.168.0.3:/mnt/share /storage/freenas -o $NFSOPTS &

To add to this. I have tested network transfer speeds in openelec (latest version for the pi 2) and the latest version of xbian for the pi 2. Samba is about the same although xbian has the edge

openelec samba 6 MB/s
xbian samba 6.5 MB/s

Where things change drastically is using NFS shares (I use hanewin where I can easily get 12 MB/s)

openelec nfs 6.2 MB/s
xbian nfs 8.8 MB/s

I repeated my transfer test multiple times. I even overclocked the pi 2 to 1100 for openelec to see if it could match xbian on NFS shares and xbian was still faster at the stock 900 Mhz than openelec at 1100 Mhz.

Have you guys encountered different pi distributions having better or worse network performance?

RE: Overclocking Pi 2 - doveman2 - 2015-03-06

(2015-03-05, 13:54)Milhouse Wrote: However, the Pi2 is easily capable of saturating the 100Mb/s network link, and it can do this without overclocking:

Code:
rpi22:~ # dd if=/storage/freenas/media/Video/test.mkv of=/dev/null 485332+1 records in 485332+1 records out 248490131 bytes (237.0MB) copied, 22.215919 seconds, 10.7MB/s

So I'd say there's something wrong with your network (router? ethernet cable?) or your NAS/NFS server, because 6MBytes/sec is way too low for a properly configured, wired, network.

Also check how you are mounting your NFS share - using larger rsize/wsize buffers and udp instead of tcp can improve throughput. This is what I have in my autostart.sh for my OS NFS mounts:

Code:
NFSOPTS=nfsvers=3,rw,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp [ ! -d /storage/freenas ] && mkdir /storage/freenas mount -t nfs 192.168.0.3:/mnt/share /storage/freenas -o $NFSOPTS &

@twelvebore, I'm using Hanewin NFS server as well and don't normally use OS NFS mounts, as the PC serving the media isn't always on but I just tried mounting as described above in Millhouse's post and got the following results from dd:

OpenELEC:/ # dd if=/storage/Media/Movies/"To Burn"/"The Tree of Life (2011).mkv"
of=/dev/null
8027987+1 records in
8027987+1 records out
4110329529 bytes (3.8GB) copied, 364.531151 seconds, 10.8MB/s

So there doesn't seem to be an issue using Hanewin. I'm not sure if there's a way to test the "normal" performance without first mounting the NFS share though, as that may well produce different results.

I'd share my Hanewin settings but they don't seem to be stored in a text file. I'll try and grab a screenshot later. This test was done running build #303 on my RPi B.

RE: Overclocking Pi 2 - twelvebore - 2015-03-07

Ace. I just re-tested using Milhouse's NFS mount settings, it gave me 11.3MB/sec.

RE: Overclocking Pi 2 - doveman2 - 2015-03-07

OK, cool. Here's my Hanewin settings which I think I arrived at following various advice on forums but it's been a long while since I set it up, so I can't be sure they're ideal.

As I said, I'm not aware of a way to test the speed without mounting as per Millhouse's settings, so I can't see how the transfer speeds compare unfortunately.

RE: Overclocking Pi 2 - popcornmix - 2015-03-07

(2015-03-07, 16:18)doveman2 Wrote: OK, cool. Here's my Hanewin settings which I think I arrived at following various advice on forums but it's been a long while since I set it up, so I can't be sure they're ideal.

Set max NFS transfer size to maximum (32768).
Enable "no count on sub-dirs"

RE: Overclocking Pi 2 - s0kkiplast - 2015-03-07

I actually got worse result from using Milhouses NFS settings than from just using smb as a source directly in kodi. I haven´t tested transfer speed but there is a sequence in a movie I have that I use for stress tests. The old Pi could not handle that sequence, it was stuttering and buffering. My overclocked Pi2 can handle it with smb but not nfs. Strange since I had much better result with nfs than smb with the old Pi...

RE: Overclocking Pi 2 - doveman2 - 2015-03-07

(2015-03-07, 17:51)popcornmix Wrote: Set max NFS transfer size to maximum (32768).
Enable "no count on sub-dirs"

Great, thanks for the tips.

RE: Overclocking Pi 2 - bagofcrap24 - 2015-03-23

I also use Hanewin and use the same tunables

Code:
Maximum NFS transfer size (32768).

Enable "no count on sub-dirs"

Tests are using the new "storage-name.mount" method of system mounting

Code:
[Mount]

What=192.168.1.60:/MyTVShows

Where=/storage/anime

Options=nfsvers=3,intr,noatime,rsize=32768,wsize=32768,nolock,async,proto=udp

Type=nfs

reboot performed between each test

1st attempt

Code:
OpenELECPi2:~ # dd if=/storage/anime/test.mkv of=/dev/null

612798+1 records in

612798+1 records out

313752614 bytes (299.2MB) copied, 26.235381 seconds, 11.4MB/s

2nd attempt

Code:
OpenELECPi2:~ # dd if=/storage/anime/test.mkv of=/dev/null

612798+1 records in

612798+1 records out

313752614 bytes (299.2MB) copied, 26.234982 seconds, 11.4MB/s

3rd attempt

Code:
OpenELECPi2:~ # dd if=/storage/anime/test.mkv of=/dev/null

612798+1 records in

612798+1 records out

313752614 bytes (299.2MB) copied, 26.240541 seconds, 11.4MB/s

So a consistent 11.4MB which isn't bad to say the theoretical max is 12.5MB/s
I'd have to agree that the Kodi internal nfs mounts lack of options is likely the cause of the slowdowns

RE: Overclocking Pi 2 - slackpy - 2015-04-26

Hi

New to the forum here Smile

I'm looking for suggestions for safe values to overclock my RPI2.

Here's my current setup:

No cooler
No heatsinks
Standard plastic case
2 Amps Power Supply
Kingston 2GB Micro SD (002 A00LF)
Edimax EW-7811Un 802.11n Wireless Adapter

/boot on SD Card
/storage on external powered usb 2TB hdd

skin: Amber

OpenELEC:~ # lsb_release
OpenELEC (official) - Version: 5.0.7

OpenELEC:~ # vcgencmd get_config int
arm_control=0xa5800010
arm_freq=900
avoid_fix_ts=1
config_hdmi_boost=2
disable_commandline_tags=2
disable_l2cache=1
emmc_pll_core=1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
hdmi_force_cec_address=65535
hdmi_ignore_cec_init=1
ignore_lcd=1
over_voltage_avs=0x1b774
pause_burst_frames=1
program_serial_random=1
sdram_freq=450
temp_limit=85

I don't know if this is relevant but I live in a tropical country where it's easy to reach 35°C most part of the year.

I'm open to use testbuids and buying heatsinks.

Thanks in advance for your suggestions.

RE: Overclocking Pi 2 - wrxtasy - 2015-04-27

Hot here in Oz as well in Summer, I would not worry about frying the RPi2 even when Turbo Overclocked.
No Heatsinks needed.

Just use the standard Turbo Settings that are listed in the OpenElec config.txt file.
You will very likely not be able to push the RPi2 and have a stable system past these settings.
5V/2.0Amp Power supply a must.

Turbo Overclock:
arm_freq=1000
core_freq=500
sdram_freq500
over_voltage=6
over_voltage_sdram=4
force_turbo=1

Smile

RE: Overclocking Pi 2 - slackpy - 2015-04-28

Hi man,

I'll try this later today.

Thanks for your reply Smile

(2015-04-27, 05:32)wrxtasy Wrote: Hot here in Oz as well in Summer, I would not worry about frying the RPi2 even when Turbo Overclocked.
No Heatsinks needed.

Just use the standard Turbo Settings that are listed in the OpenElec config.txt file.
You will very likely not be able to push the RPi2 and have a stable system past these settings.
5V/2.0Amp Power supply a must.

Turbo Overclock:
arm_freq=1000
core_freq=500
sdram_freq500
over_voltage=6
over_voltage_sdram=4
force_turbo=1

RE: Overclocking Pi 2 - cudencuden - 2015-05-12

(2015-04-27, 05:32)wrxtasy Wrote: Hot here in Oz as well in Summer, I would not worry about frying the RPi2 even when Turbo Overclocked.
No Heatsinks needed.

Just use the standard Turbo Settings that are listed in the OpenElec config.txt file.
You will very likely not be able to push the RPi2 and have a stable system past these settings.
5V/2.0Amp Power supply a must.

Turbo Overclock:
arm_freq=1000
core_freq=500
sdram_freq500
over_voltage=6
over_voltage_sdram=4
force_turbo=1

wrote these settings last night. thanks,