The Chromebook Pixel Review
by Jason Inofuentes on May 31, 2013 8:00 AM ESTThe Memory Issue
Memory has long been an issue for Chromebooks, but I didn’t understand why until recently. The incredibly high pixel count certainly wasn’t going to help things. To find out how they might cope with this issue, we caught up with Caesar Sengupta, Product Manager at Google for Chrome OS. I've never understood why Chromebooks always come with modest memory on-board. It isn’t a cost issue, certainly; memory is cheap. It's soldered on, and comes in denser packages so it’s not likely a space issue. Google's making a conscious choice to go small with memory. So, how do you cope 4 million pixels and just 4GB RAM? In this case, the first step is to render all pages at 1280 x 800, unless HiDPI assets are available. The final product is upscaled to the full 2560 x 1600, but the memory doesn’t take nearly the punishing you might expect; unless, of course, every site you visit has HiDPI assets.
Then there’s a user behavior problem that has long plagued Chrome OS. Tabs linger and multiply. An untidy user could tax the memory assets of any system with tab after tab of unread longreads and cat GIFs. With memory taxed, the OS will begin shuffling under used bits of data into a swap file on local storage, effectively an extension of system memory stored on your hard drive. Even the fastest SSDs are several orders of magnitude slower than RAM, so switching to a tab whose contents had been pushed to the swap file would briefly yield a blank screen as the content is brought back to system memory. The developers of Chrome OS had a mission: an operating system that lives and breathes entirely within system memory. That means, no swap file. And that means an often frustrating user experience.
That same untidy user could bring a Chromebook to its knees with open tabs, and with no swap file, pages purged from memory are simply refreshed when focus is restored. Not that big of a deal, right? Say those tabs are actually your site’s content management system and dozens of tabs of research. Further, that you’ve just spent an hour putting together a great post, and tabbed away just long enough to verify a bit of research. Switch back to your CMS, the page refreshes, and your great post disappears into the ether. Surely, there's a better alternative. Please?
The Chrome OS BSOD (plus touch indicators)
Android enthusiasts will be familiar with compcache, a method of creating a compressed page file on system memory that can help alleviate memory shortages. Now called zram, this technique fits perfectly within Chrome's philosophy of speed over all other factors. Local storage options vary too much in speed for their speed targets with Chrome, so operating even the page file within memory is a logical step. In practice, zram is better, not great. When a page is purged completely, you get the Chrome BSOD equivalent and an option to reload. This alleviates system slow downs that arose from automatically refreshing each page as you tabbed through them. I haven't noticed any particular slow down that might indicate that a given page's data was being recalled from zram, which could be a good sign. But there's no changing the fact that slicing a piece away from that 4GB for use as a page file isn't nearly as effective as adding another 4GB.
Facebook
Twitter
RSS
74 Comments
View All Comments
Spoony - Friday, May 31, 2013 - link
No way. It must render the page at 1280x800, scale it up, then over the top draw native text. There is simply no way Jason wouldn't have complained bitterly if all of the text was jaggy.lmcd - Friday, May 31, 2013 - link
You realize that text is always available at high DPI as they're usually scalable vectors, right? But regardless of rendered size they're the same size, right?Oh. Yeah, don't forget that!
tuxRoller - Friday, May 31, 2013 - link
Always love hearing what will never be the case for things that don't involve tautologies:)Selden - Saturday, June 1, 2013 - link
Text is razor sharp.jeffkro - Monday, June 3, 2013 - link
You miss the point of the OS, its a no fuss more secure OS. Sure you can do more with windows but for some people its to complicated. I also don't like the idea of some hacker in Russia hacking into windows and getting all my banking info.Selden - Wednesday, August 7, 2013 - link
@JDG1980 : No, you get razor-sharp text, as shown in a screenshot. I just went through cataract surgery, and I have been able to go down a few points in text sizes, and 10-20% on screen magnification with the Pixel, also lower brightness, which increases battery life.cjb110 - Friday, May 31, 2013 - link
One thing they should port is their new Android Studio!lmcd - Friday, May 31, 2013 - link
Well, that's dependent on the moment on their work with NaCl. Hopefully PNaCl final comes out soon (with the performance promised). That, and I hope Dart turns out. Dart + PNaCl looks promising enough to deliver an Android Studio experience.shompa - Friday, May 31, 2013 - link
I try to think of one single reason to buy Chromebook instead of a rMBP (beside the stupid "I hate Apple").Apple have an OS that is designed for retina displays. Apple have solved the issue with non native resolution by render the original screen at 4 times its pixel count and downscale it make it look good on a 2880x1440 screen.
Why have tons of specs when it cant be used? And 4 gig memory?
I hope that Google releases an Android version of Chroomebook. The same day Android can/is preinstalled on PCs, thats the same day that MSFT for the first time have had competition. Something that all consumers would win by.
mavere - Friday, May 31, 2013 - link
I think they should have went with a slightly slower, cheaper Intel chip and spent that extra money on more RAM. It seems like the software offers the expectation of multitasking that the hardware fails to meet.The Chromebook design screams "I do one thing but I do it well". Uhh not at 4GB RAM, you don't.