On Thu, Feb 02, 2006 at 04:17:56AM -0800, Roman wrote:
> I don't think it's filesystem related, i.e. there is not much I/O happening
> at the time. Maybe NetBSD's /bin/sh is a lot faster than Solaris
> /bin/{sh,ksh,bash}, maybe NetBSD's fork() is a lot faster. I didn't benchmark
> the two operat
I've used gethrtime on both
Roman wrote:
I don't think it's filesystem related, i.e. there is not much I/O happening at
the time. Maybe NetBSD's /bin/sh is a lot faster than Solaris
/bin/{sh,ksh,bash}, maybe NetBSD's fork() is a lot faster. I didn't benchmark
the two operating systems. I'm h
I don't think it's filesystem related, i.e. there is not much I/O happening at
the time. Maybe NetBSD's /bin/sh is a lot faster than Solaris
/bin/{sh,ksh,bash}, maybe NetBSD's fork() is a lot faster. I didn't benchmark
the two operating systems. I'm hoping to conduct some benchmarks soon and wil
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
I use an Ultra 10 at home with 640 MB of RAM and a 120 GB disk using a Creator
graphics card. As long as I don't use Gnome or JDS performance is fine. When
you installed Solaris, did you perform a Full Distribution installation? If so
there are a few things you can shut off that will free some m
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 pai
