Home/ Questions/Q 802285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T23:34:38+00:00

I’m looking into writing an Android game, tough I don’t curerntly own an Android

  • 0

I’m looking into writing an Android game, tough I don’t curerntly own an Android device. For those of you who own a device, how does the performance on the emulator relate to real device performance? I’m especially interested in graphics related tasks.

This obviously depends on both the machine running the emulator, and the specific device in question, but I’m talking rough numbers here.

This question is a duplicate, but since that post is heavily outdated, I figured it’s irrelevant by now.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally speaking, the emulator is much slower than a device at CPU and GPU tasks. That’s for at least two reasons:

    1. The emulator is running ARM opcodes, converting them into equivalent x86 instructions, which is slow
    2. Devices (usually) have graphics accelerators, whereas the emulated environment does not, despite whatever video card you have on the machine running the emulator

    To put things in perspective, I do my Android work on an Intel quad-core 2.66GHz with a fairly nice graphics card. For videos that work fine on devices, I can sometimes get them to play back in the emulator.

    The emulator is faster than a device, though, at “disk” I/O. When you write to “flash” on the emulator, you are writing to a disk image file that probably resides on a regular hard drive, assuming you’re not using an SSD. Actually writing to flash on a device can be massively slower — Brad Fitzpatrick, at last week’s Google I|O 2010 conference, cited spikes of up to 200ms to write a single byte to flash. And, the combination of Android, flash, and the yaffs2 filesystem apparently causes a device to get progressively slower at flash I/O as the flash fills up. Hence, his recommendation was to do any flash writes in a background thread instead of the main application thread, where it can tie up the UI and lead to a “janky” app.

    (apparently, “janky” is a technical term… 🙂

    BTW, when it shows up online, definitely watch Brad’s presentation on YouTube. It may be a bit difficult to follow at times, because he spoke very quickly, but it was full of useful tidbits related to performance.

    • 0