WizardStan
Mega GP Mania
- Joined
- May 24, 2008
- Messages
- 16,733
The Pyra doesn't have a 64 bit CPU.Regardless, moot, since Minecraft has a 64-bit version.
The Pyra doesn't have a 64 bit CPU.Regardless, moot, since Minecraft has a 64-bit version.
Right, but I was saying that there was a 64-bit version of Minecraft, so if a 64-bit CPU comes out eventually for the Pyra, it'd be fully possible for it to run the 64-bit version of Minecraft.The Pyra doesn't have a 64 bit CPU.
Yes, but that has no bearing on the current discussion of whether 4GB in the Pyra would benefit Minecraft or not.Right, but I was saying that there was a 64-bit version of Minecraft, so if a 64-bit CPU comes out eventually for the Pyra, it'd be fully possible for it to run the 64-bit version of Minecraft.
Yes, and that's the trickier question to answer.Yes, but that has no bearing on the current discussion of whether 4GB in the Pyra would benefit Minecraft or not.
I agree, and over time I have seen several reasons why I feel ARM was the right choice. A couple that really bother me personally are this feeling I get that we wouldn't get optimized software because people would say why bother (I hope this is all in my head), and that it would be compared even more than it currently is to x86 devices with a similar form factor. For me the Pyra is greater than the specs and being a clamshell with a keyboard, just as the Pandora is, and the DOS based palmtops have been for their hardcore fans (because they still have a place in the world today, and it is on the frontlines, not sitting in the back of a drawer).(Maybe a Cortex-A57? Granted, we'd probably have to move away from OMAP for those... there hasn't been a new OMAP product since 2013. With Tegra out, Atom and Snapdragon are the two most likely candidates, but obviously Atom isn't ARM... at this point, an updated CPU board is sounding more like it'd be a full-on system rewrite to support it, ack.)
If the boards have to be reduced to 2GB, I don't know if I'd be still willing to keep up with the pre-order to be completely honest.
As I would be paying a premium for postage and the device that would be kinda underpowered to something like a GPD-Win which is quite a bit cheaper.
The absolute main reason I pre-ordered the pyra was for 3G web browsing which takes quite a chunk of the ram out.
I wouldn't mind the extra voltage for the extra 2GB but hopefully there will be a better solution.
That was a guy called m@t, I think he got bannedNope it was not you. This person we later found out hasn't preordered.. Come to think of it I havent seen them around in a while.
Oh wow, maybe I should use Linux more!Ah well, that's Windows for you.
Here is a screenshot of my current desktop:
As you can see, it runs Plasma (KDE5), FreeCad, Gimp, Evolution Mail (with calendar, task and contacts sync running), MoneyPlex, some smaller tools (like Kate, Speedcrunch, Konsole), and Nextcloud (can't be seen in the picture though).
All at the same time. And the memory usage is still under 2GB RAM, and that's a 1920x1080-resolution.
Plasma alone uses 600MB of RAM, Evolution about 200MB (it really eats a lot of memory).
The browser (with all the tabs you can see here) uses around 300MB of RAM.
This is certainly a lot more that I ever want to run on a Pyra at the same time (FreeCAD and Gimp...? )
If I switched to something like LXDE on my laptop, the full memory usage would be around 1.3GB for all of that.
So yeah... 2GB is plenty, as long as you don't use anything that simply hogs the memory for some reason
I still want to get the 4GB Pyra working though
So you compare x86-64 memory usage to armhf (32) and expect the same behaviourAs you can see it already needs more than 2GB of RAM right after starting. The memory usage will get up while Programming/Debugging.
So: This is a real-life example where 2GB of RAM is clearly not sufficient....
So you compare x86-64 memory usage to armhf (32) and expect the same behaviour
Also screen size make a huge difference in memory usage. FullHD double the memory consomption compared to 720p.
But yeah 4GB can be nice for that kind of usage though
This distinction may be a little subtle for some (one?) but what I was (and still am) pushing for was for a 2GB Pyra and a 4GB to be tested side by side to see how much benefit is gained from the additional 2GB of Ram. So when people pre ordered a Pyra they would know whether the extra cost of a 4GB unit was worthwhile expenditure.Yes inadequately researched and ill-conceived. Seems to have been offered as a result of irrational community pressures before it could be properly researched.
Doubt all you want. Read the history and the piles of posts from @Mr_Loon pushing for it
Sounds like a test with a board running the mobile / low voltage version would be a sensible way to proceed.Now, I love hanging out on the IRC channel.
I was so amused when I got to read that the wrong memory chip had been used in the 4GB samples. We got the usual version, not the mobile/low voltage version. There was checking that needed to be done to find out if we ordered the wrong model number or whether the wrong one was delivered. I was surprised that a post wasn't made to update the crowd regarding the issue. I hope that I'm not breaking any unwritten (or written) guideline by forwarding this information. I hope that I don't take any thunder away from an ED post.
We already ordered samples of a different RAM Chip (also 4GB in total size) by a different manufacturer.
We'll populate one PCB with those. If that chip works, we can pretty much rule out 1.
Err nope, not at all. A 64b OS have all its instructions coded on 64b while a 32b OS have all it's instructions coded on 32b. That mean the binary size on 32b is half the size of on 64b systems (not exactly but you now have an idea). Beside, Pointers and some other datatypes doesnt have the same size. So the same code compiled as 32b and as 64b will not consume the same memory... at all... then you have the difference between the 2 architectures where the compiler does not produce that same optimisations (SSE vs NEON etc).But I think it will be similar...
...except that it's hard to find a fixed length ISA nowadays (and even on those a 64bit architecture does not have to use 64bit instructions), x86 always used variable length instructions. And you don't stuff your RAM full of assembly, you make it burst with data.A 64b OS have all its instructions coded on 64b while a 32b OS have all it's instructions coded on 32b.
I was so amused when I got to read that the wrong memory chip had been used in the 4GB samples. We got the usual version, not the mobile/low voltage version. There was checking that needed to be done to find out if we ordered the wrong model number or whether the wrong one was delivered. I was surprised that a post wasn't made to update the crowd regarding the issue.