Brian Feldman <gr...@unixhelp.org> writes:
> > One way of tackling the problem is - to implement per lock profiling
> > and detect which locks are being contested heavily and try breaking
> > them down. That would be a practical way of doing things.
>
> But you can't generalize FreeBSD's usage, can you?
>
While it's true that no one can see all possible uses of FreeBSD, one
has to make assumptions about the typical usage - web server, file
server etc and use it as the design center, while making sure that it
doesn't perform too badly on other less common workloads.
-Arun
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
