search for: virtbench

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode) ./virtbench local...

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode) ./virtbench local...

Hi all, I've been working on a set of easy-to-run benchmarks for hypervisor optimization called virtbench, and the latest commit adds Xen support. http://ozlabs.org/~rusty/virtbench http://ozlabs.org/~rusty/virtbench/?archive/tip.tar.bz2 >From the README: # Build the code make # Set the guest kernel location and maybe more vi ./SETTINGS # Run the benchmark (local mode) ./virtbench local...

Hi all, I got few servers to make xen nodes, to evaluate maybe other virtualisation and different xen configurations... I don`t know match about benchmarking, I was wondering what and how to test properly Dom0 and DomU performance on different servers... If somebody is interested in results I can publish them... thanx, Casper _______________________________________________ Xen-users

...d. Using 512mb, the build time goes from 10.75 minutes to 9 minutes. For 512mb, native is around 7 minutes so that's pretty close to what Avi had seen. The more dramatic improvement with large memory guests is probably because of the increased shadow page table activity due to high mem. virtbench shows major improvements but I'm not 100% confident yet in the results as they are not very stable. I don't yet have a benchmark that shows the benefit of the CR caching so if I don't find one, I'll drop that from the queue. As usual, the latest bits are available at http://hg...

...d. Using 512mb, the build time goes from 10.75 minutes to 9 minutes. For 512mb, native is around 7 minutes so that's pretty close to what Avi had seen. The more dramatic improvement with large memory guests is probably because of the increased shadow page table activity due to high mem. virtbench shows major improvements but I'm not 100% confident yet in the results as they are not very stable. I don't yet have a benchmark that shows the benefit of the CR caching so if I don't find one, I'll drop that from the queue. As usual, the latest bits are available at http://hg...

...ng code means that we don't actually have to do as much work in lguest's patcher. We use paravirt_patch_default() for cases we don't want to patch inline, which automatically handles the "patch iret to use a direct jump" case. There's no measurable effect on lguest's virtbench scores tho. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/lguest.c | 10 ++-------- drivers/lguest/lguest_asm.S | 1 - 2 files changed, 2 insertions(+), 9 deletions(-) =================================================================== --- a/drivers/lgues...

...ng code means that we don't actually have to do as much work in lguest's patcher. We use paravirt_patch_default() for cases we don't want to patch inline, which automatically handles the "patch iret to use a direct jump" case. There's no measurable effect on lguest's virtbench scores tho. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/lguest.c | 10 ++-------- drivers/lguest/lguest_asm.S | 1 - 2 files changed, 2 insertions(+), 9 deletions(-) =================================================================== --- a/drivers/lgues...