From owner-freebsd-xen@freebsd.org Tue Feb 7 17:01:13 2017 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD0BBCD5FB0 for ; Tue, 7 Feb 2017 17:01:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 668C51C8F for ; Tue, 7 Feb 2017 17:01:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v17H1CIY071430 for ; Tue, 7 Feb 2017 17:01:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 212681] I/O is slow for FreeBSD DOMu on XenServer Date: Tue, 07 Feb 2017 17:01:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rainer@ultra-secure.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 17:01:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681 --- Comment #23 from rainer@ultra-secure.de --- Which event specifier should I use? I can't even run the sample: (freebsd11 ) 0 # pmcstat =E2=80=93S RESOURCE_STALLS.ANY -O out.pmcst= at sleep 10 pmcstat: [options] [commandline] Measure process and/or system performance using hardware performance monitoring counters. Options include: -C (toggle) show cumulative counts -D path create profiles in directory "path" -E (toggle) show counts at process exit -F file write a system-wide callgraph (Kcachegrind format)= to "file" -G file write a system-wide callgraph to "file" -M file print executable/gmon file map to "file" -N (toggle) capture callchains -O file send log output to "file" -P spec allocate a process-private sampling PMC -R file read events from "file" -S spec allocate a system-wide sampling PMC -T start in top mode -W (toggle) show counts per context switch -a file print sampled PCs and callgraph to "file" -c cpu-list set cpus for subsequent system-wide PMCs -d (toggle) track descendants -e use wide history counter for gprof(1) output -f spec pass "spec" to as plugin option -g produce gprof(1) compatible profiles -k dir set the path to the kernel -l secs set duration time -m file print sampled PCs to "file" -n rate set sampling rate -o file send print output to "file" -p spec allocate a process-private counting PMC -q suppress verbosity -r fsroot specify FS root directory -s spec allocate a system-wide counting PMC -t process-spec attach to running processes matching "process-spec" -v increase verbosity -w secs set printing time interval -z depth limit callchain display depth --=20 You are receiving this mail because: You are the assignee for the bug.=