Maxing out a Raspberry

[andrzej b]

Hi guys,

I am trying to max out my raspberry pi. I have a USB3 16gb flashdrive, Class 10 8gb sandisk SD, 1.5 amp power supply, heatsinks and a fan, running frodo. It is currently running at 109F playing a 1080 movie with 97-100% cpu usage and around 25% memory.

Can I dedicate more RAM to the GPU?
Is there a way to speed up the LAN transfer, it seems like it skips frames sometimes.

What other settings can I change to max it out?

Thanks

Here are my settings:

# default GPU memory split (do not change if you do not know what you are doing)
gpu_mem=128

# SDRAM size based GPU memory split, uncomment and setup to override 'gpu_mem'
gpu_mem_256=100
gpu_mem_512=128

################################################################################​
# Overclocking settings
# WARNING: Do not change/enable if you do not know what you are doing!
# The System may become unstable or you can have data corruption or
# you can loose your warranty if you set wrong settings
#
# please read: http://elinux.org/RPi_config.txt#Overclo...figuration
################################################################################​

# Overclock mode settings.
#
# default recommended values are: arm_freq | core_freq | sdram_freq | over_voltage
# no overclocking : 700 | 250 | 400 | 0
# mode 'Modest' : 800 | 300 | 400 | 0
# mode 'Medium' : 900 | 333 | 450 | 2
# mode 'High' : 950 | 450 | 450 | 6
# mode 'Turbo' : 1000 | 500 | 500 | 6

arm_freq=1100
core_freq=550
h264_freq=300
isp_freq=0
v3d_freq=300
sdram_freq=600
over_voltage_sdram=6
over_voltage=8
temp_limit=176
avoid_pwm_pll=1

# set to 'force_turbo=1' to disable dynamic overclocking (you can lose your warranty!)
force_turbo=1

# If you have any data corruption using Turbo Mode and overclocking
# try with this setting uncommented
# If this still fails, try to use Medium mode without "over_voltage=2"
# If it ultimately keeps failing, forget about this until it gets fixed
# Use a more conservative mode that will works fine in any cases:
# initial_turbo=30

################################################################################​
# Overscan settings
################################################################################​

# Make display smaller to stop text spilling off the screen
# see also http://www.raspberrypi.org/phpBB3/viewto...67&t=15700
# overscan_scale=1
# disable_overscan=1

# Adapt overscan values to your needs
# overscan_left=57
# overscan_right=59
# overscan_top=20
# overscan_bottom=20

################################################################################​
# various settings see also: http://elinux.org/RPi_config.txt
################################################################################​

# Force HDMI even if unplugged or powered off
# hdmi_force_hotplug=1

################################################################################​
# License keys to enable GPU hardware decoding for various codecs
# to obtain keys visit the shop at http://www.raspberrypi.com
################################################################################​

# decode_MPG2=0x00000000
# decode_WVC1=0x00000000
# decode_DTS=0x00000000
# decode_DDP=0x00000000

################################################################################​
# End of default configuration
# all values below this line were inserted from config.txt.bk (your old config)
# and can be merged with the above values
################################################################################​

[RobHenry]

Heatsinks and fan are unnecessary, unless you think they look good.

You could allocate more ram to the gpu, but I don't think it will ever need more than the 128MB you have given it.

It shouldn't be using 97-100 % cpu playing 1080p movies, it's usual for cpu usage to be high when using the gui and considerably lower when playing a movie. I'm not sure why you might be seeing usage this high.

You don't mention what os you are using. Reports are mixed, and very subjective, but I find openelec to be the most efficient in terms of the load that it puts onto the device (this is a contentious point and it won't be long before someone comes along and states that raspbmc puts less strain on the pi).

Your overclock settings are around the highest that have been reported to work so it looks like you're pretty close to the limit of how far you can soup up the device.

[GTR2Fan]

1/ You've set the temperature limit to over twice the recommended safe maximum, so it's effectively disabled and worthless.

2/ You've disabled thermal throttling by forcing the overclock with 'force_turbo=1', not that it's going to work properly anyway (see #1).

3/ You've set the ARM voltage potentially dangerously high.

4/ The RAM is being over-volted to the safe maximum limit which most likely isn't even necessary.

5/ The settings you've used have blown the warranty bit, so you no longer have a manufacturer's guarantee.

Not wishing to sound rude, but if you're trying to kill your Pi then you're going the right way about it.

[andrzej b]

1/ You've set the temperature limit to over twice the recommended safe maximum, so it's effectively disabled and worthless.

2/ You've disabled thermal throttling by forcing the overclock with 'force_turbo=1', not that it's going to work properly anyway (see #1).

3/ You've set the ARM voltage potentially dangerously high.

4/ The RAM is being over-volted to the safe maximum limit which most likely isn't even necessary.

5/ The settings you've used have blown the warranty bit, so you no longer have a manufacturer's guarantee.

Not wishing to sound rude, but if you're trying to kill your Pi then you're going the right way about it.

Thanks for stating the obvious and not answering any of the questions.
1. The temp is in Fahrenheit.
2. Yes, I want it running at full speed all the time.
3. Probably, now do you think I can get more out with this?
4. Yes, as stated, I am trying to max it out.
5. Obviously I don't care about the warranty. I am not rich, but loss of $35 is not the end of the world.

Thanks

[ragnarjensen]

1. The temp is in Fahrenheit.

No, the temp limit is in Celsius. Your 176 C is 348.8 F
--
Ragnar

[chrisryall]

What is a Fahrenheit? I'm 61 now and have used the Internationally standard C system since I was 15.

Encourage anyone else interested in the future to do the same!

[andrzej b]

1. The temp is in Fahrenheit.

No, the temp limit is in Celsius. Your 176 C is 348.8 F
--
Ragnar

Doesn't it depend on the time zone setting? I read somewhere that it does, and since I'm in US, it's "Standard".

Well, it doesn't matter, what is the max limit, 80C? my temp is nowhere near that.

[andrzej b]

What is a Fahrenheit? I'm 61 now and have used the Internationally standard C system since I was 15.

Encourage anyone else interested in the future to do the same!

You know, USA has to be different; so, it will stick with the past.

[andrzej b]

Come on guys, does anyone have anything constructive to say on the subject and not just "smart" remarks? I know you're all smart, and don't need to be proving it by pointing out meaningless and obvious things.

[andrzej b]

Ok, I installed Gotham and increased arm and core frequencies. It is noticeably faster, and the cpu usage felt 20% (at around 80%) while playing the same 1080 movie. The temp is at 115F, 46C for my metric friends, while playing a 1080 movie. Arm freq of 1200 would cause the xbmc to freeze.
How can I stress test it? And what else can I do to max it out?

arm_freq=1150
core_freq=600
h264_freq=300
isp_freq=0
v3d_freq=300
sdram_freq=600
over_voltage_sdram=6
over_voltage=8
temp_limit=176
avoid_pwm_pll=1

[ragnarjensen]

Doesn't it depend on the time zone setting?

config.txt is read before the Pi has any notion of what time zones are.

How can I stress test it?

You could try something computationally intensive. Compute PI to a couple of million decimals. And build a Linux kernel at the same time.

--
Ragnar

[ghans]

Try running Samba and sharing an external (NTFS) harddisk ,
then from a Windows client run a random access benchmark
on the share.

Should be close to real-world usage and put a lot of stress on
the Pi , especially through the USB subsytem. Should heat up
the LAN9512 nicely , too.


ghans

[GTR2Fan]

...what is the max limit, 80C? my temp is nowhere near that.

The maximum guaranteed safe temperature is 85°C. If you remove your 'temp_limit' entry then it defaults to that. Setting 'force_turbo=0' will have no effect on performance whatsoever unless the hardware is getting dangerously hot.

There are plenty of benchmarks and a few stress tests available HERE.

Heatsinks and even a fan are necessary under some circumstances when overclocking and running very demanding applications despite many saying otherwise. Mine certainly gets very close to the 85°C limit when running certain games even with a small heatsink, and that's at an ambient room temperature of 20°C, so I'm looking to improve the cooling before summer arrives to prevent thermal-throttling.

Now I know that your Pi is dispensible, enjoy pushing it until it probably goes pop.

[andrzej b]

Doesn't it depend on the time zone setting?

config.txt is read before the Pi has any notion of what time zones are.

How can I stress test it?

You could try something computationally intensive. Compute PI to a couple of million decimals. And build a Linux kernel at the same time.

--
Ragnar

Makes sense. Will change that.

Can you walk me through the stress test, or link me to a site? I know almost nothing about linux.

[andrzej b]

Try running Samba and sharing an external (NTFS) harddisk ,
then from a Windows client run a random access benchmark
on the share.

Should be close to real-world usage and put a lot of stress on
the Pi , especially through the USB subsytem. Should heat up
the LAN9512 nicely , too.


ghans

That is my setuIp now. I'm connecting to the windows homegroup through Samba, and that is how I play the movies. The LAN does heat up (too hot to touch for more than a second), although now with the heatsink and the fan, it is probably 20 degrees cooler.

After installing Ghotham, it doesn't seem like it is dropping frames anymore.
Can you walk me through on how to run a random access benchmark

[andrzej b]

...what is the max limit, 80C? my temp is nowhere near that.

The maximum guaranteed safe temperature is 85°C. If you remove your 'temp_limit' entry then it defaults to that. Setting 'force_turbo=0' will have no effect on performance whatsoever unless the hardware is getting dangerously hot.

There are plenty of benchmarks and a few stress tests available HERE.

Heatsinks and even a fan are necessary under some circumstances when overclocking and running very demanding applications despite many saying otherwise. Mine certainly gets very close to the 85°C limit when running certain games even with a small heatsink, and that's at an ambient room temperature of 20°C, so I'm looking to improve the cooling before summer arrives to prevent thermal-throttling.

Now I know that your Pi is dispensible, enjoy pushing it until it probably goes pop.

Yeah, I just removed the entry.

I'll check those benchmarks out.

LoL, will do enjoy, and will let you know when it pops

[andrzej b]

...what is the max limit, 80C? my temp is nowhere near that.

The maximum guaranteed safe temperature is 85°C. If you remove your 'temp_limit' entry then it defaults to that. Setting 'force_turbo=0' will have no effect on performance whatsoever unless the hardware is getting dangerously hot.

There are plenty of benchmarks and a few stress tests available HERE.

Heatsinks and even a fan are necessary under some circumstances when overclocking and running very demanding applications despite many saying otherwise. Mine certainly gets very close to the 85°C limit when running certain games even with a small heatsink, and that's at an ambient room temperature of 20°C, so I'm looking to improve the cooling before summer arrives to prevent thermal-throttling.

Now I know that your Pi is dispensible, enjoy pushing it until it probably goes pop.

Ok, I am a noob. I got lost at the site; too many words and choices.
I have downloaded the Raspberry pi benchmark zip. Unpacked it. What do I do now? I am on windows 7, connected to raspberry pi by LAN switch.
How do I run these benchmarks... can you give me step by step...

[R1nzler]

Ide use magnets....MAGNETS

[Richard-TX]

I think the question is what else can you do to get more performance?

As far as I am concerned the biggest throttle on the Rpi's performance is the IO bandwidth. It is also the one thing that can't be improved on as a user.

You have overclocked it to the max so nothing else is left there.

The next thing is use and tuning. If you use a gui desktop, then running the X server on another computer should help overall performance. Even better is not running any X applications.

I believe you are done. You have found the "Go faster" knob and cranked it to the max. Nothing else is left except a fork-lift upgrade.

Richard

PS. I have played with overclocking for years and in general it just doesn't pay. All works well until one day the system won't boot or it starts crashing. Lower the clock speed and then it boots again. What happened? Obviously the die in the CPU chip aged and now it won't run as fast. The one overclock that did work well was raising the clock speed of a WE32000 CPU. I raised the clock speed by about 20% and it still worked but it was the traces on the motherboard that was the limiting factor on that chip. A good board would work right when overclocked. A early board would not.

[andrzej b]

Is 600 the limit for gpu core and sdram? Cause I can go higher, just don't know if it is actually working, or if it is just defaulting to 600. Note I am using openelec

[andrzej b]

I think the question is what else can you do to get more performance?

I believe you are done. You have found the "Go faster" knob and cranked it to the max. Nothing else is left except a fork-lift upgrade.

Yeah, that may be the limit. Well, had fun overcklocking it.

[andrzej b]

Ide use magnets....MAGNETS

I will definitely give those a try!

[mlarma]

I've been running with the following settings for like ever. Notice that the ratios are in sync with one another. That was intentional. Never did testing to verify it was faster, but based on prior experiences in the PC world, asynchronous interfaces create waits. Info on this from others would be helpful. I also use heatsinks, which helped get to these levels safely and temps stay low. Without them, it would not only be completely unstable, it would more than likely fail.

arm_freq=1100
force_turbo=1
core_freq=550
sdram_freq=550
h264_freq=275
isp_freq=275
v3d_freq=275
over_voltage=8

Not related to the settings above, I also allocate 128MB to the GPU on my Pi B.

gpu_mem=128

Cheers,

Mark

[AndrewS]

Sounds like people are looking for this thread: http://www.raspberrypi.org/forums/viewt ... =29&t=6201

[Wommit]

1. The temp is in Fahrenheit.

No, the temp limit is in Celsius. Your 176 C is 348.8 F
--
Ragnar

348F !!!!!

Isn't that over the spontainious combustion point?

I thing he might have noticed if his Pi started burning.

Just sayin' like.

Wommit