Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upWhy does qvm-run from VM to VM take a quarter of a second? #2274
Comments
andrewdavidwong
added
bug
C: core
labels
Aug 29, 2016
andrewdavidwong
added this to the Release 3.2 milestone
Aug 29, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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?
|
Most of the time (all of it?) is spent on running qrexec-policy. It is Best Regards, |
Rudd-O commentedAug 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 completetrue.Thanks.