base OS image sizes for KVM and LXC are different due to their different virtualization mechanisms, but this has no bearing in our results since, in our experiments, the base layer resides in every MEC and is not included in the migration. As we see below, the installation footprint of applications can be larger for LXC than for KVM, because the Ubuntu installation of LXC has fewer packages included as standard. As such, the installation of any missing packages is counted into the LXC application size.

We studied the migration of the following applications using our migration framework presented above.

1.  *Game Server* runs the *sauerbraten-server* package, a server for the online game Cube 2. It sends and receives regular packets related to player location and other match statistics. The installation footprint is very small ($0.7$ MB), as is the memory requirement (approximately $1$ MB).

2.  *RAM Simulation* is a simple script (approximately $0.1$ MB) that consumes a large amount of RAM, where the exact RAM consumption is user-defined and the RAM contents keep changing over time. It represents memory intensive applications, such as those that process large data sets or perform complex calculations (e.g., big data analysis, training of 