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

Why does qvm-run from VM to VM take a quarter of a second? #2274

Open
Rudd-O opened this Issue Aug 29, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@Rudd-O

Rudd-O commented Aug 29, 2016

Latest R3.2b packages. qvm-run somevm true (with policy already accepted) takes 0.260 s. This is making bombshell take about a half a second just to complete true.

Thanks.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 30, 2016

Member

Most of the time (all of it?) is spent on running qrexec-policy. It is
standalone python script and I bet importing modules takes the most of
its run time. It can be improved by implementing simple
qrexec-policy-daemon, which would respond for policy requests, but
currently it is rather low priority task. If you like, you can work on
this...

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Aug 30, 2016

Most of the time (all of it?) is spent on running qrexec-policy. It is
standalone python script and I bet importing modules takes the most of
its run time. It can be improved by implementing simple
qrexec-policy-daemon, which would respond for policy requests, but
currently it is rather low priority task. If you like, you can work on
this...

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

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