Skip to content

Assess the performance of firecracker on aarch64 #875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dianpopa opened this issue Jan 22, 2019 · 5 comments
Closed

Assess the performance of firecracker on aarch64 #875

dianpopa opened this issue Jan 22, 2019 · 5 comments
Assignees
@dianpopa
Labels
Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled `
Milestone
ARM Support

Comments

@dianpopa
Copy link
Contributor

Create benchmarks for the aarch64 firecracker microVMs to extract performance metrics.
@dianpopa dianpopa changed the title Asses the performance of firecracker on aarch64 Assess the performance of firecracker on aarch64 Jan 22, 2019
@xiaobo55x
Copy link

@dianpopa
Hi,

Here is Haibo, from ARM open source software team.
We are very interested in this project, and have tried to launch the MicroVM on our x86_64 platform. Meanwhile, we noticed that firecracker is successfully built on aarch64 platform according to #756 .
Very appreciate that if you could share more status and road map about the firecracker support on aarch64. Also, please let us know if we can provide some help for this task.

Regards,

Haibo

@dianpopa
Copy link
Contributor Author

Hi @xiaobo55x ,
I am really glad about your interest in this feature and really appreciate your support.
Indeed, the project should compile on aarch64. However, we still do not have a CI test that makes sure the build does not get broken when a PR is merged but we are trying to get as close as possible to that point.
It is worth mentioning that up until now I encountered no major issue implementing the specific aarch64 functionality since you have great documentation. Congrats on that!
We keep track of progress on enabling firecracker on aarch64 by logging issues that are labeled with the Feature: ARM Support. As far as the current status, I am currently working at implementing the FDT for the microVM and looking forward to pushing the "spawn" button in the near future.
Make sure you join our slack channel so that it is easier to ping you in case I need help with this.

@xiaobo55x
Copy link

Hi @dianpopa ,

Thanks for sharing! I have joint your slack channel with the username "haibo xu".
Please ping me if we can do any help.

Regards,

Haibo

@raduweiss raduweiss modified the milestone: ARM Support Feb 15, 2019
@raduweiss raduweiss added the Priority: High Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled label Feb 15, 2019
@dianpopa dianpopa added Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` and removed Priority: High Indicates than an issue or pull request should be resolved ahead of issues or pull requests labelled labels Mar 15, 2019
@dianpopa
Copy link
Contributor Author

All performance related CI successfully pass on aarch64 without adjustments.
The block device I/O overhead is tracked in #1529 .

@dianpopa
Copy link
Contributor Author

Nothing is left to be done on aarch64 here. Performance improvements will be treated equally on all architectures from now on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dianpopa dianpopa

Labels
Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled `
Projects
None yet
Milestone
ARM Support
Development

No branches or pull requests
3 participants
@dianpopa @xiaobo55x @raduweiss