Analyzing 4GB RAM


I pre-ordered a 4GB version but I can go with a 2GB if that becomes the case, in fact seeing it being such a issue to get it to work for so long kinda makes me wish 4GB never was an option. Especially since when Pyra pre-orders has been meet and it's in stock to buy the question on peoples mind will probably be "when will there be a SoC-Board upgrade to the OMAP5?" None the less I always have the stands that ED should take his time :) and I'm happy to see that you took some time off to get some rest.
 
4GB or nothing.
CuSSpeFUsAAqOsv.jpg
 
Many thanks for the update @EvilDragon .

What would be useful to me (and I suspect a few others) would be a comparative test of a 2GB board and a 4GB board showing the impact on battery life & performance (ram vs swap). I understand it's difficult to get a good test for swap performance so even a qualitative assessment of some kind would be useful.

Sounds like the solution to the 4GB issue is frustratingly close to being found, best of luck with the new tests.
 
Another update: 1.5V with DLL off booted up my 4GB system without issues. Haven't done much, but it usually already froze when booting. 6 minutes uptime without any issue.
I'll let it run for a while.

Still up and running at the desktop. Need to run memtester at some time though.
And 1.5V is not really an option, but a test...

However: If that works, it probably means that our voltage drop is too high but the noise is not that much of an issue.
That should be an easier fix.

... and it's still running.
2,5 hours now. Good sign, as it shows that basically nothing is wrong with our software setup here, and the hardware fix shouldn't be too hard.


Very good news! \:D/ \:D/ \:D/

thanks for the updates ;)
 
[…]
15.4 MiB + 9.1 MiB = 24.5 MiB caja
23.8 MiB + 944.5 KiB = 24.7 MiB named
25.0 MiB + 4.4 MiB = 29.4 MiB terminator
30.8 MiB + 5.0 MiB = 35.7 MiB hexchat
41.1 MiB + 25.9 MiB = 67.0 MiB Xorg
51.0 MiB + 31.1 MiB = 82.1 MiB Web Content
81.9 MiB + 895.0 KiB = 82.8 MiB tor (2)
86.2 MiB + 6.1 MiB = 92.3 MiB rhythmbox
236.1 MiB + 37.6 MiB = 273.8 MiB firefox
308.9 MiB + 4.8 MiB = 313.7 MiB thunderbird (2)
767.5 MiB + 14.9 MiB = 782.4 MiB firefox-esr
1.6 GiB + 9.6 MiB = 1.6 GiB Grim Dawn.exe
---------------------------------
3.8 GiB

Here’s ps_mem.py¹ on my desktop. So I think I could actually use those 4GB…

---
¹ github.com/pixelb/ps_mem
 
Assuming that new CPU board will be prepared much faster than the whole project, the 2G option don't seem to sound so bad.

But seeing current progress on the issue makes me optimistic about it.

On the progress side, are the cases ready yet?
 
[…]
3.8 GiB

Here’s ps_mem.py¹ on my desktop. So I think I could actually use those 4GB…

Code:
....
82.2 MiB +   7.0 MiB =  89.2 MiB    nginx (35)
 96.3 MiB + 116.0 KiB =  96.4 MiB    prometheus
 70.6 MiB +  32.5 MiB = 103.1 MiB    xfdesktop
114.2 MiB +   2.2 MiB = 116.5 MiB    netdata
 95.5 MiB +  38.6 MiB = 134.0 MiB    postgres (47)
128.5 MiB +  24.2 MiB = 152.7 MiB    soffice.bin
 84.6 MiB + 120.8 MiB = 205.4 MiB    rsync (3)
333.0 MiB +   4.2 MiB = 337.2 MiB    quodlibet
 62.8 MiB + 403.1 MiB = 465.9 MiB    Xorg
499.3 MiB +  86.0 MiB = 585.3 MiB    okular (4)
565.0 MiB +  39.5 MiB = 604.5 MiB    thunderbird [updated]
636.3 MiB + 550.0 KiB = 636.8 MiB    qemu-system-x86_64 [updated]
  2.2 GiB +  10.6 MiB =   2.2 GiB    bundle (6)
  2.8 GiB + 107.4 MiB =   2.9 GiB    chromium-browser (42)
  2.5 GiB + 542.9 MiB =   3.0 GiB    firefox
  5.1 GiB + 370.9 MiB =   5.4 GiB    Web Content (4)
---------------------------------
                         18.0 GiB
=================================

oops. I guess no handheld will do if i use my desktop as reference.
 
I would actually like to switch to a 2GB model, regardless if it's needed or not for the simple reason that I could get my Pyra in the first batch and because of the outlook of a lower power consumption, since I want my Pyra to be on 24/7 as a personal assistant/console to my servers.
I also believe that I can work with 2 GB RAM no problem.
 
I would most definitely take a 2GB 4G Pyra for my prototype pre-pre-order AND would spend the additional 25EUR +/- on a processor board keychain - preferably a populated errata (non-working) board.

Far too much time & money has been spent on the unneeded scope creep that is the 4GB RAM issue. Upgraded specs to RAM & eMMC could all have been part of a later upgrade board still using the OMAP5432.

So - working on a hypothetical...
500 boards get populated as 2GB units.
Early production losses are going to be high-ish, maybe 5-10% as there has been little chance for board population process refinement.
Likely 450-475 solid 2GB units can get shipped. Population failure boards marketed as keychains for 25EUR each? (No that does not cover the value of the components installed - but we're talking about unusable board population failures here and simply saving them from the landfill.)

Maybe 2-3 weeks to get 2GB board population into the schedule for the pick & place then a day to populate and another 2 weeks to assemble & test units. 1.5 Months?

Main boards with corrected antennas will need some time to get created & populated. Together that is probably 2 Months?

Cases...???

Are Christmas 2017 Pyra consoles in user hands a hypothetical possibility? Wishful thinking?
 
Ugh... I wanted to refrain from actually commenting on the whole RAM debate, but I would like to add my two cents worth now:

I can understand, that for some the 4gb RAM seems like feature/spec creep, but for me this was actually a reason for buying. I would like a device that is capable of running a modern full feature browser and consequently it should also be able to display the various (bloated) dynamic websites of today. I want to use the pyra as a development machine and since I am now developing using the google app engine framework, running a server locally becomes an issue with 2gb ram. I would have to run the dev_appserver, have an IDE open (preferably something similar to pycharm with syntax hightlighting and python linter) and a webbrowser at the same time, as a minimum. Now if I have a tab open with jira, the google dev console, the admin panel of my current project and a view of the actual page, this quickly becomes a 1.8gb instance. add to that a fully featured IDE/code editor and the server app and I am not sure the setup as such is feasible.

Otherwise the pyra is not really much use over my panoras. Yes, a lot more media capable perhaps an we will be able to emulate the dreamcast... but I already have a dreamcast at home.

Also I am not sure if a cpu board will ever see the light of day at all.

I guess I'd need to reevaluate the purchase of a pyra if it was only available with 2gb. I'll definitely wait for some thorough testing and feedback from the community before I spent my hard earned cash, which will mean, that I will have to wait a longer time anyway.

Obviously wishful thinking will not force the 4gb ram to suddenly work. I am just surprised that everyone who wants to accelerate the process by cutting the 4gb version seems to believe that an upgrade will be available which I was under the impression of being more of a vague and uncertain "perhaps" rather than a definitive plan for the future.
 
I would like a device that is capable of running a modern full feature browser and consequently it should also be able to display the various (bloated) dynamic websites of today. I want to use the pyra as a development machine and since I am now developing using the google app engine framework, running a server locally becomes an issue with 2gb ram. I would have to run the dev_appserver, have an IDE open (preferably something similar to pycharm with syntax hightlighting and python linter) and a webbrowser at the same time, as a minimum. Now if I have a tab open with jira, the google dev console, the admin panel of my current project and a view of the actual page, this quickly becomes a 1.8gb instance. add to that a fully featured IDE/code editor and the server app and I am not sure the setup as such is feasible.

Look up Notaz's video TRYING to max out the ram. He had like 50 tabs, music, two instances of his playstation emulator, eclipse and a bunch of other crap....all on 2 GB
 
Did you miss me?
Yes, how did you know? ;) Hopefully the bicycle thief got to feel the Wrath of the EvilDragon (upcoming exclusive Pyra game?), and maybe a black eye to go with it.

As a vocal supporter of "MOAR RAM", once again I say I am fine accepting standard 2GB if this becomes the thing holding everything up. Either (or both, CPU board to go with my signed main board! and an upgrade later) of your other suggestions work for me, and I will opt for the 2GB model with reduced cost "upgrade" board if I can afford it. Consider me option A to help get things moving (for others, I am fine waiting if you get the numbers you need).

I thought you were going to use the 1GB chip for the 4GB Pyras. Would that be a possible fix?

I am not at all upset by the news, and I fully support whatever you need to do.
 
4 GB Partialy Working with 1.5 Volt?
Sound good ..even its in testing State. ;)

I have no Problems with have 2 Omaps and 2 GB of each then.

One Omap5(where the Grafics are used) as Main CPU and the other Omap5 only as Co Cpu and for accolating the other 2GB Ram??
Then we have Quadcore Pyra with 4 Gigabyte Ram? :D
Is that not a possible Way too?

No Problem for me to downgrade to the 2 GB Version when no other Way is there..because i can Swap Memory ;)
 
Back
Top