Skip to content

Welcome to vAccel

vAccel is a framework offering hardware acceleration primitive with focus on portability. It exposes to programmers "accelerate-able" functions and abstracts away hardware complexity by means of a pluggable design.

The design goals of vAccel are:

  1. portability: vAccel applications can be deployed in machines with different hardware accelerators without re-writing or re-compilation.
  2. security: A vAccel application can be deployed, as is, in a VM to ensure isolation in multi-tenant environments. QEMU and AWS Firecracker VMMs are currently supported
  3. compatibility: vAccel supports the OCI container format through integration with the Kata containers framework.
  4. low-overhead: vAccel uses a very efficient transport layer for offloading acceleratable functions from insde the VM to the host, incuring minimum overhead.
  5. scalability: Integration with k8s allows deployment of vAccel applications at scale.

vAccel design

vAccel runtime stack

The core component of vAccel is the vaccel runtime (vAccelRT). vAccelRT is designed in a modular way. The core runtime exposes the vAccel API to user applications and dispatches requests to one of many backend plugins, which are the components that implement the vAccel API on a particular hardware accelerator.

The user application links against the core runtime library and the plugin modules are loaded at runtime by the runtime. This workflow decouples the application from the hardware accelerator-specific parts of the stack, allowing for seamless migration of the same binary to different platforms with different accelerator capabilities, without the need to recomplile user code.

Currently, we support acceleration plugins for:

  1. Jetson inference framework, for acceleration of ML operation on Nvidia GPUs.
  2. Google Coral TPU, for acceleration on Coral TPUs.

Hardware acceleration in Virtual Machines

Hardware acceleration for virtualized guests is a difficult problem to tackle. Typical solutions involve device pass-through or paravirtual drivers that expose hardware semantics inside the guest. vAccel differentiates itself from these approaches by exposing coarse grain "acceleratable" functions in the guest over a custom transport layer.

The semantics of the transport layer are hidden from the programmer. A vAccel application that runs on baremetal with an Nvidia GPU can run as is inside a VM using our appropriate VirtIO backend plugin.

We have implemented the necessary parts for our VirtIO driver in our forks of QEMU and Firecracker hypervisors.


vAccel performance overhead of VM execution compared to bare-metal

The above figure depicts a performance comparison of the image classification operation of a vAccel application running inside a Firecracker VM using the Jetson inference plugin comparing to an execution of the same operation using the Jetson inference framework natively without any vAccel code, running directly on the host.

The performance overhead of our stack is less that 5% of the native execution time across a range of image sizes.

We will be updating these performance results regularly with more operations and plugins.