Roman wrote:
I use both official Solaris 10 and Nevada build 28.
I don't even have to measure time, you can tell forks
are slow just by looking at it. Like I said I build
software from pkgsrc, many packages have GNU configure
scripts that fork and execute small test programs.
On Solaris those scripts run painfully slow (yes I've
tried bash and ksh, it makes no difference) and on
NetBSD things are so much faster.
This message posted from opensolaris.org
I'm impressed that you are able to distinguish fork slowness from
exec slowness by just watching the output from configure... I'm
forced to use libmicro to gather actual data :-).
There are things in Solaris that are slower than other
operating systems. We haven't spent a lot of time optimizing small
process fork performance, and many of our very short cmds do
more localization processing on startup than is actually necessary.
If you're interested, I suggest that running libmicro on NetBSD
might be an interesting exercise. It's always good to collect
actual data; what at first seems like a fork performance problem
sometimes turns into static vs dynamic linking, etc.
Also, what kind of hardware are you running on?
- Bart
--
Bart Smaalders Solaris Kernel Performance
[EMAIL PROTECTED] http://blogs.sun.com/barts
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
