3 ms·
More info on how we use it on AWS Firecracker is available on our blog post: https://blog.cloudkernels.net/posts/vaccel_v2/ https://blog.cloudkernels.net/posts/
by _ananos_ 6y ago
More info on how we use it on AWS Firecracker is available on our blog post: https://blog.cloudkernels.net/posts/vaccel_v2/ https://blog.cloudkernels.net/posts/vaccel_v2/ and our github pages: https://github.com/cloudkernels/vaccelRT https://github.com/cloudkernels/vaccelRT, https://github.com/nubificus/docker-jetson-inference https://github.com/nubificus/docker-jetson-inference
- landerwust 6y agoThe block diagram here: https://blog.cloudkernels.net/static/vaccel_v2/vaccelrt.png#center https://blog.cloudkernels.net/static/vaccel_v2/vaccelrt.png#... should probably have some close variant on your home page, I've been around for 20 years and couldn't tell /at all/ what vAccel is. My best guess was something to do with making VMs run faster
- _ananos_ 6y agothanks for your feedback! we will try to clarify things on our next posts! in short vAccel is a framework that translates function calls from users (upper side of this diagram) to the relevant functions of the respective acceleration framework (lower side of the diagram). For instance, calling a function like image_classify (user function) would result in the respective image_classify of jetson-inference, which would, in turn, execute the image classification function on the GPU and return the result to the user. hope that makes more sense!