Linked by Thom Holwerda on Tue 19th Dec 2017 19:22 UTC

Today, we are excited to announce Quick Boot for the Android Emulator. With Quick Boot, you can launch the Android Emulator in under 6 seconds. Quick Boot works by snapshotting an emulator session so you can reload in seconds. Quick Boot was first released with Android Studio 3.0 in the canary update channel and we are excited to release the feature as a stable update today.

There's a quite a few other improvements and new features, as well.

Permalink for comment 652300
To read all comments associated with this story, please click here.
Member since:

In all honestly most of the complexity is bloat. Even linus torvalds has acknwoledged linux has a bloat problem. Android is tuned for very specific hardware. If the kernel on your android phone does "support 1000 upon 1000 of CPU types, chipsets, devices, etc.", then whoever built it did a pretty bad job in trimming it down to only the hardware present on the device. Know what I mean? The build it supposed to be optimized for that specific hardware.

The OP in this sub thread was comparing C64 to a PC. He wasn't talking about Android, nor was I.

Arguably not true by performance per clock...

Actually, The amount of rows/sec PostgreSQL -on- Linux can store or index is billion years a head of any database that existed in the C64 or even the early PC days. Even if you generate odd matrices such as rows/sec per Mhz or rows/second per disk RPM, the performance difference is simply staggering.
Same goes for networking (packets/sec per Mhz) and graphics (triangles/sec per Mhz).

Sure, but it doesn't explain why the overhead is so much greater.

Sure it does.
Back in the C64 or even in the XT days, a graphics card was nothing more than a dual ported memory chip.
Today a graphics card is a hugh-SMP CPU that's expected to push billions of vertices and handle complex requests simultaneously. How can you possibly expect to continue program such a beast by calling 'int 10h'?

Networking is no different. How can you possibly compare a C64 modem that was barely cable of pushing 1200bps via the simplest of interfaces (serial port) to a multi-PCI-E 100GbE network device that includes smart buffering, packet filtering and load-balancing?

IMHO it's true of most code.

Being a system developer I can't say that I care much for user facing code ;)

- Gilboa

Edited 2017-12-21 13:22 UTC

Reply Parent Score: 4