Quoting Dan Lukes <[EMAIL PROTECTED]> (from Thu, 12 Oct 2006 09:43:20 +0200):
[moved from security@ to [EMAIL PROTECTED]
The main problem is - 6.x is still not competitive replacement for
4.x. I'm NOT speaking about old unsupported hardware - I speaked about
performance in some situation and believe in it's stability.
You can't be sure that a committer has the resources to setup an
environment where he is able to reproduce your performance problems.
You on the other hand have hands-on experience with the performance
problem. If you are able to setup a -current system (because there are
changes which may affect performance already, and it is the place
where the nuw stuff will be developt) which exposes the bad behavior,
you could make yourself familiar with the pmc framework
(http://wiki.freebsd.org/PmcTools, I'm sure jkoshy@ will help if you
have questions) and point out the bottlenecks on current@ and/or
performance@ (something similar happened for MySQL, and now we have a
webpage in the wiki about it). Without such reports, we can't handle
the issue.
Further discussion about this should happen in performance@ or [EMAIL PROTECTED]
Bye,
Alexander.
--
"A penny for your thoughts?"
"A dollar for your death."
-- The Odd Couple
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
_______________________________________________
freebsd-performance@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
