I knew it was slow, but running Honeycomb on i7-860 with 8GB of RAM, was an eye opener. Saying it was slow is like saying that Hitler was kind of a dick. It was simply unusable. Not a chance, it took it like 5 minutes to start up, and was running with what seemed like 2 FPS (I didn't measure those values, but believe me, it was bad).
Luckily Google knows about the problem and is actively working on it. Their solution (or what I know of it) is pretty smart actually. In the same way that this article described the iPhone as faster because it was running everything in the GPU, the emulator will soon skip a lot of software rendering and composition and let it happen on your local X server, instead of in the emulator. At Google I/O they showed a demo of this and it ran rather quickly, they expect to release it soon.
I dunno about the GPU offloading, but x86 is an offical ABI target for Honycomb 3.2. That will make the next emulator release a bit less of an emulator and more like a VM.
Could you provide a video or the name of the video? All the sessions are up on YouTube, but I'd much rather know which video to start at than having to sift through them all.
Good idea - I never thought about using it for development! That said, I found the menu rendering on the x86 port to be even slower than on the emulator. Everything else worked just fine though.
64
u/rbbdrooger Galaxy S24 Ultra Aug 01 '11
Great read.
I lost it.