Run many Android emulator instances on one server

Android emulators can run several instances at once, each a separate Android system with its own apps and accounts. Each emulator has a manager for this. This guide shows how to use them and how to size instances so the server stays responsive.

Before you start

• A running emulator on your Android GPU server; see Android emulator servers: getting started.
• An idea of the resources one instance of your app needs (start one instance and watch it in Task Manager).

Step 1: Open the multi-instance manager

Step 2: Create instances

In the manager, add an instance:

• Fresh instance: a clean Android system. Choose the Android version and the instance's CPU and memory if the manager asks.
• Clone: a copy of an existing instance with its apps and settings. Set up one instance completely, then clone it.

Start each instance from the manager's list. In BlueStacks, the manager's + Instance button starts the creation; in MEmu, Multi-MEmu offers new, clone and start for each instance.

Verify: each instance appears in the manager and opens its own window.

Step 3: Size the instances to the server

All instances share the server's processor, memory and graphics resources. A rule that keeps the server responsive:

1. Start one instance with your app and note its CPU and memory use in Task Manager.
2. Add instances one at a time and watch the totals.
3. Keep total memory use clearly below the server's memory, and leave CPU headroom for Windows and the emulator's own processes.
4. Reduce per-instance resolution and frame rate if you run many instances; most automation does not need full HD at 60 FPS.

If the instances need more than the server has, move to a larger plan; see upgrade or downgrade a service.

Step 4: Arrange and start instances efficiently

• Use the manager's batch start or start all functions where available, and stagger the start: starting many instances at the same moment loads the disk and CPU heavily.
• Use the manager's window arrangement options to tile the windows.
• Give instances clear names (app, account), so you know which is which after a restart.

Troubleshooting

New instances fail to start or crash. The server is out of memory. Stop instances you do not need, or reduce memory per instance.

Instances become slow after a while. Check CPU and memory in Task Manager; one instance may use far more than the others. Restart it, and check the app's own settings.

The manager's shortcut does nothing. The emulator is not up to date, or the manager is reached differently in your version. Update the emulator from its official website.

More fixes: Android emulator troubleshooting.

Next steps

• Back to the basics: Android emulator servers: getting started.
• Linux servers: Android Emulator on a Linux server.