> pmcannotate is a tool that prints out sources of a tool (in C or
> assembly) with inlined profiling informations retrieved by a prior
> pmcstat analysis.
[snip]
> This work has been developed on the behalf of Nokia with important
> feedbacks and directions from Jeff Roberson.
Are you "rookie"
> Thanks, I have already found this. There was only problem, that by
> default it counts cycles only when both logical cores are active while
> one of my cores was halted.
Did you try the 'active' event modifier: "p4-global-power-events,active=any"?
> Sampling on this, profiler shown results clos
> I have tried it for measuring number of instructions. But I am in doubt
> that instructions is a correct counter for performance measurement as
> different instructions may have very different execution times depending
> on many reasons, like cache misses and current memory traffic. I have
> trie
mc> Also make sure that you don't use a giant-locked driver
mc> somewhere in the chain to the filessystem and that WITNESS
mc> and friends are off. Is this a SMP machine?
As a general suggestion, you can use hwpmc(4) and pmcstat(8)
to understand where the bottlenecks are. For example, you
can c
lh> Is the fsync() on FreeBSD6.1 fake?
It doesn't appear to be:
sys/kern/vfs_syscalls.c: 3194: fsync(td, uap)
sys/ufs/ffs/ffs_vnops.c: 175: ffs_fsync(struct vop_fsync_args *ap)
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-pe
> Our current Dells have 2M cache, and I'm trying to determine
> whether the 8M cache will make a significant difference or
> not. Can someone recommend a testing procedure for
> determining whether adding cache is worthwhile or not?
> I can simulate a test load at any time, but I don't know how
>
> here are ktrace results for supersmack and mysqld from a dualcore opteron box
> running select smack with 100 threads and 1 queries
> os: fbsd 6.1 prerelease
>
> syscall stats for supersmack
> number of syscalls captured: 42575687
> individual syscalls counts:
>read 32914539
bj> I am lookign for good and reliable profiling tools that work
bj> on FreeBSD.
What is wrong with the current tools?
bj> Also is
bj> there any GUI on top of gprof
Kprof -- http://kprof.sourceforge.net/
There are probably others too.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
> So here's the problem, I've got a DB server that needs a
> large datasize and a tomcat server which occasionally needs
> to use a lot of memory, which java allocates from a memory
> mapped space. Any ideas how to get the system to allow
> processes to have either/or?
IIRC, the process layout is
On 11/15/05, Ashok Shrestha <[EMAIL PROTECTED]> wrote:
> I'm using MySQL 5.0.15 with FreeBSD 5.4-RELEASE amd64.
> I would like to get the maximum performance out of this box.
> What options (MAKE, kernel, etc...) should I use to achieve
> this? What about loading the INDEX file into memory?
You m
On 10/24/05, Lukas Razik <[EMAIL PROTECTED]> wrote:
>
> O.K.
>
> I've found the reason for the issue.
> After exchanging the newer
> src/sys/i386/include/cpufunc.h,v 1.142.6.1 2005/05/13 00:12:57
> src/sys/i386/i386/mp_machdep.c,v 1.235.2.6.2.3 2005/05/13 00:12:56
> from 5.4-RELEASE-p1 by the old
>
> Is there a way to find out which program(s) are causing
> the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-performance@freebsd.org mailing list
http://lists.
Question in $subject, thanks.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-performance@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> RAM/address space is the big reason. In fact, applications
> compiled for 64-bits may well run slower than 32-bit ones
> running on the 64-bit kernel.
On the other hand we have 16 registers to play with on the AMD64
and they can be used far more orthogonally than on the i386.
That would cut d
A new snapshot of the CPU PMC driver and associated userland tools
is available.
o Support for performance monitoring counters in Intel(r) Pentium
Pro, Pentium-II, Pentium-III, Celeron and Pentium-M has been
added.
o A Python interface to libpmc has been added.
o Many bug fixes, esp. for P4
15 matches
Mail list logo