search for: lmbench

...is approach is slow. The benchmarks were done on a UP 3GHz Pentium 4 with 512MB of RAM. 2.6.17-rc4 vs 2.6.17-rc4 with CONFIG_PARAVIRT=y vs 2.6.17-rc4 CONFIG_PARAVIRT=y with patch. Summary: with binary patching, the difference from CONFIG_PARAVIRT=n is in the noise (with the possible exception of lmbench's exec). Full results can be found in subdirs of http://kernel.org/pub/linux/kernel/people/rusty/Paravirt/stats The patch sites are 10-12 bytes long; we can shave more bytes off by telling GCC we clobber regs. The Xen SMP cli() code might actually need more bytes than this, but I haven't...

...is approach is slow. The benchmarks were done on a UP 3GHz Pentium 4 with 512MB of RAM. 2.6.17-rc4 vs 2.6.17-rc4 with CONFIG_PARAVIRT=y vs 2.6.17-rc4 CONFIG_PARAVIRT=y with patch. Summary: with binary patching, the difference from CONFIG_PARAVIRT=n is in the noise (with the possible exception of lmbench's exec). Full results can be found in subdirs of http://kernel.org/pub/linux/kernel/people/rusty/Paravirt/stats The patch sites are 10-12 bytes long; we can shave more bytes off by telling GCC we clobber regs. The Xen SMP cli() code might actually need more bytes than this, but I haven't...

Hey everyone, I hope you guys can help me explaining a pretty strange result that came up when benchmarking a native Red Hat installation against a Xen DomU (installed in a file container). I used lmbench3 on a dualcore AMD-machine. To make the results comparable, I "unplugged" all CPU cores but one in the native installation (setting the "online"-entry to 0). The DomU had only one vCPU assigned. The installed packages on both machines were identical as well. After doing the init...

Hey everyone, I hope you guys can help me explaining a pretty strange result that came up when benchmarking a native Red Hat installation against a Xen DomU (installed in a file container). I used lmbench3 on a dualcore AMD-machine. To make the results comparable, I "unplugged" all CPU cores but one in the native installation (setting the "online"-entry to 0). The DomU had only one vCPU assigned. The installed packages on both machines were identical as well. After doing the init...

In OLS 2005, we described the work that we have been doing in VMware with respect a common interface for paravirtualization of Linux. We shared the general vision in Rik's virtualization BoF. This note is an update on our further work on the Virtual Machine Interface, VMI. The patches provided have been tested on 2.6.16-rc6. We are currently recollecting performance information for the new

In OLS 2005, we described the work that we have been doing in VMware with respect a common interface for paravirtualization of Linux. We shared the general vision in Rik's virtualization BoF. This note is an update on our further work on the Virtual Machine Interface, VMI. The patches provided have been tested on 2.6.16-rc6. We are currently recollecting performance information for the new

Hi all, I''ve performed a benchmark on my server to compare performance with and without Xen, and with and without domUs active. I used lmbench to measure basic hardware operations on math and memory, and system calls like mmap(), fork(), exec(). The results are at http://drainbamage.nl/2009/04/05/xen-benchmark/ . It seems that Xen adds significant overhead to process creation routines (fork, exec) and mmap and page faults. Howe...

...: RHEL4 U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) Scheduler : credit TEST RESULT DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA and Fujitsu members _______________________________________________ Xen-devel mailing list Xen-devel@l...

...U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) CONFIG_QEMU : ioemu-remote TEST RESULTS DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA Shin''ya and Fujitsu members _______________________________________________ Xen-devel mailing...

...: RHEL4 U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) Scheduler : credit TEST RESULT DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA and Fujitsu members _______________________________________________ Xen-ia64-devel mailing list Xen-ia...

...OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) Scheduler : credit TEST RESULT DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20061121 : 19/831 FAIL (see attachment) iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20061121 : 1/831 FAIL iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA and Fujitsu members _______________________________________________ Xen-ia64-devel mailing list...

...U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) CONFIG_QEMU : ioemu-remote TEST RESULTS DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5 : Pass Best regards, KUWAMURA Shin''ya and Fujitsu members _______________________________________________ Xen-ia64-devel ma...

...run the 1-way test on 32 bit to show the same problem. So, I have run with writable PTs and with emulation forced on for several benchmarks: on Xeon MP processor, uniprocessor dom0 kernel, pae=y: benchmark c/s 10729 force_emulate ------------------------ --------- ------------- lmbench fork+exit: 469.5833 470.3913 usec, lower is better lmbench fork+execve: 1241.0000 1225.7778 usec, lower is better lmbench fork+/sbin/bash: 12190.000 12119.000 usec, lower is better dbench 3.03 186.354 191.278 MB/sec reaim_aim9 1890.01 2055.97 jobs...

...c/extract-table.pl Binary-package: bk2site (1:1.1.9-3.1) file: /usr/lib/cgi-bin/bk2site/redirect.pl Binary-package: datafreedom-perl (0.1.7-1) file: /usr/bin/dfxml-invoice Binary-package: emacs-jabber (0.7.91-1) file: /usr/lib/emacsen-common/packages/install/emacs-jabber Binary-package: lmbench (3.0-a7-1) file: /usr/lib/lmbench/scripts/rccs file: /usr/lib/lmbench/scripts/STUFF Binary-package: rancid-util (2.3.2~a8-1) file: /var/lib/rancid/getipacctg Binary-package: ogle (0.9.2-5.2) file: /usr/lib/ogle/ogle_audio_debug file: /usr/lib/ogle/ogle_cli_debug file: /usr/l...

...system_call jumped up quite a lot. Using TCP streaming test as a > workload and running on 32-bit 2.6.20 kernel, system_call goes up from > 0.00025% all the way to 1.6% in the oprofile data. There is a drop of > about 4% in overall throughput for this particular workload. > > With lmbench's null system call test, the call time goes up from 0.10 > usec to 0.225 usec. > > I'm testing on dual socket Intel core 2 processor running at 2.67 GHz > with 4 GB RAM. [ I assume you're talking about running on native hardware. ] In the current paravirt changes in the ker...

Hi, I have used lmbench to test the performance of Xenolinux (HVM) CPU: Intel (R) Core (TM)2 T7400@2.16GHz Memory size: 1GB NIC: Intel PCIe Gigabit LAN chip HD: Samsung 80GB/7200rpm/8M Dom0: 2.6.19-1.2911.6.5.fc6xen DomU: 2.6.20-1.2944.fc6 The context switch time seems saturated along with increasement of processes?...

...OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) Scheduler : credit TEST RESULT DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20061121 : 19/831 FAIL (see attachment) iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: (not tested) Best regards, KUWAMURA and Fujitsu members _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

...performance became better especially with workloads that require heavy memory management operations. On 8-way x86_64 xenlinux (dom0) the kernel build was improved by about 10% (using make -j32). Even a small setup like a UP HT system, I see about 3% performance gain with kernel build (make -j4). Lmbench also shows improvements in fork/exec/sh: Processor, Processes - times in microseconds - smaller is better -------------------------------------------------------------------- Host OS Mhz null null open slct sig sig fork exec sh call I/O stat clos TCP inst hndl pro...

...OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS : RHEL4 U2 (8P, with PV-on-HVM drivers) Scheduler : credit TEST RESULT DomU: unixbench4.1.0 : Pass bonnie++-1.03 : Pass ltp-full-20061121 : 18/831 FAIL (see attachment) iozone3_191 : Pass lmbench-3.0-a5 : Pass DomVTi: (not tested) Best regards, KUWAMURA and Fujitsu members _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel

...system_call jumped up quite a lot. Using TCP streaming test as a > workload and running on 32-bit 2.6.20 kernel, system_call goes up from > 0.00025% all the way to 1.6% in the oprofile data. There is a drop of > about 4% in overall throughput for this particular workload. > > With lmbench's null system call test, the call time goes up from 0.10 > usec to 0.225 usec. > > I'm testing on dual socket Intel core 2 processor running at 2.67 GHz > with 4 GB RAM. [ I assume you're talking about running on native hardware. ] In the current paravirt changes in the ker...