Skip to content
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.

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

CVM-IO Motivation #44

Open
enterJazz opened this issue Jan 8, 2024 · 2 comments
Open

CVM-IO Motivation #44

enterJazz opened this issue Jan 8, 2024 · 2 comments

Comments

@enterJazz
Copy link
Contributor

Motivate CVM IO

Disk I/O from CVMs experiences the worst performance impact, with up to 56% overhead, while network I/O experiences up to 36% overhead.

  • own eval results: SEV + TDX
    Screenshot from 2024-01-08 at 13_44_25 303219100
@enterJazz
Copy link
Contributor Author

ISSUE

Project does currently NOT convince Pramod.

As discussed w/ Peter and @mmisono , the current 'lack' of overhead gap is due to virtio-blk backend use.

  • as shown in Spool: major differences in virtio-blk and SPDK performance!
    Screenshot from 2024-01-17 at 14_21_32 600362721
  • virtio-blk is presumably a botteleneck when it comes to performance differences
    • hence: performance differences are being watered out!

ISSUE:

  • we can't directly compare native VM w/ SPDK and CVM w/ SPDK
    • we can't confirm bottleneck in this way

INSTEAD:
We can either:
i. do measurements to show that virtio-blk is indeed taking up most of the performance
ii. or: compare virito-blk w/ spdk directly -> argue that perf difference shows bottleneck

either i or ii, we need to show that CVM drawbacks make a large difference when SPDK is used

@enterJazz
Copy link
Contributor Author

@mmisono

I reran swiotlb benchmarks w/ native (unmodified, diff branch) kernel, to ensure we didn't make a mistake.
Saw minimal perf difference, so current measurements are correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant