From owner-freebsd-current Tue Sep 12 10:53:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id A2BF937B43E; Tue, 12 Sep 2000 10:53:24 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e8CHrOQ02801; Tue, 12 Sep 2000 10:53:24 -0700 Date: Tue, 12 Sep 2000 10:53:24 -0700 From: Brooks Davis To: Nik Clayton Cc: current@FreeBSD.ORG Subject: Re: VMWare on -current, how fast should I expect it to be? Message-ID: <20000912105324.A31617@Odin.AC.HMC.Edu> References: <20000912142745.A7121@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000912142745.A7121@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Tue, Sep 12, 2000 at 02:27:45PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 02:27:45PM +0100, Nik Clayton wrote: > For those of you running VMWare (2) on -current, how fast do you expect it to > be? I'm running it on my PIII 366 laptop. It's not great, but it's usable. The biggest factors I've seen effecting performance are memory related. Running out will cause the system to temporarily hang while it pages large chunks of memory in and out. Also, the J option to malloc did really bad things to performance when I had it on. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message