I'm working on improving the performance of Python on Solaris
using profile-based optimisations, as described here:
http://wikis.sun.com/display/AppPerfTuning/Python
I'm using parrotbench and also a few simple pkg commands
to gather statistics. I'm wondering if you could suggest
more ways to exercise code paths in pkg and especially
ones that are CPU-hungry.
I'm currently doing these:
./python /usr/bin/pkg list -av
./python /usr/bin/pkg search -l /usr/bin/pkg
pfexec ./python pkg rebuild-index || true
./python /usr/lib/pkg.depotd -p 64433 -d /var/pkg/repo \
--readonly --exit-ready
Using these and parrotbench makes a significant difference
but I'd like to do even more.
Making an installation plan seems like a good candidate,
but I'd like to do things that won't actually change the
build system.
Any suggestions?
Thanks
Laca
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
