Running Ubuntu off an SDCard on the new ARM Chromebook
plus.google.com
plus.google.com
Once you put in the order you can forget about getting any useful support when you notice a mistake like this. All I've been able to get out of their support is the same automated email sent to me about 10 times in response to my various queries. They are simultaneously (on different pages) telling me it is too late to cancel the order and yet the order won't ship until the 24th...
For a company that basically lives and breathes the web, Google ought to be totally ashamed at how god awful their online order support is. I've dealt with dozens of mom and pop online shops that run circles around this bullshit.
In the future I'll be sure to just be patient and wait for Amazon or someone else I can trust to get online retail right to have the item in stock.
However this is basically a 2 year old prototype and it still serves me very well.
I'm probably just being dense, but why would an application want to know anything at all about the hardware underlying a directory? (It could probably parse /etc/mtab and make an educated guess, but why go to the trouble in the first place?)
More likely, it's pattern of fs access aren't ideal for an SD card.
Well, this makes sense.
I only looked into it briefly but it seemed complicated for me to set that up. Bonus points, new macs use EFI rather than standard BIOS, which seemed to make things even more confusing.
But it has proved to be plausible. A gloss for those in the same boat as I was:
I just did a "hdparm -tT /dev/sda" on my bluelight-special 5400 rpm laptop drive and it is getting 3,100 MB/sec cached reads. The absolute fastest reads I see reported with the Sandisk Ultra cards on Amazon is 45 MB/s, with a few 30 MB/s reads, and mostly 20 MB/s reads.
Something doesn't add up here.
But the thing that really matters for bootup time, application load time, and application responsiveness time is 4k random reads. And 4k random reads for my bluelight-special 5400 rpm drive are:
4K random reads: 494 KB/s (KB!!!)[0]
According to the number one google result for "4k random read sandisk ultra"[1]:
4k random speeds: 4,499 KB/s
There are definitely some older SSDs that come in at around 2,350 KB/s (6,000 iops) for their 4k random reads.
So moral of the story: just buy a new SSD already with 4k random reads of 250,000+ KB/s.
[0] Using iozone. command:
iozone -e -I -a -s 50M -r 4k -i 0 -i 1 -i 2
[1] http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=4...That is cached or buffered reads.[0] The buffer appears to be a small amount of memory that sits on the HDD. In addition to housekeeping, it seems mostly useful for read-ahead, which seems like it helps a little bit when you are accessing the same part of the HDD repeatedly (i.e., usually). On my HDD it is 8 GB.
RAM is faster than cache though. My RAM has a peak transfer rate of 10666 MB/s (DDR3 1333). Stuff sits around in your RAM after being loaded until something else needs the space. So buffers help with initial loads from the HDD. But after that, RAM is king.
For sequential reads/writes to my actual disk, the speeds are 15,000 KB/s to 50,000 KB/s (faster for larger files).
So yeah. SSD still the way to go for any form-factor that can handle it. But it's nice to know that SD cards have gotten to the point where they rival and sometimes beat HDDs in terms of real-world performance. The range of possible applications for the Pi and its ilk just expanded in my mind.
Yay, learning!
In the ok range, I could get work done-- chrome, emacs, and a web stack running. Page loads revere slow, but usable. I don't think I'd set a machine up this way again, it's just too much of a pain for what I'm getting out of it.
To get it to boot, all you really need to do is make sure that you use GRUB2 and do an EFI install to the external SSD. (Ubuntu will do this automatically, as will Fedora and no doubt others). (I want to say that rEFIt would handle this no matter what, but I can't remember even with my own MBA when USB will work with the EFI->BIOS bridge.
The only shame is that the Chromebook doesn't seem to come with a UHS-1 [1] interface, just SDHC/SDXC