Beginner questions

"John D. Mitchell" <johnm@cory.EECS.Berkeley.EDU>
Errors-To: brian@grot.starconn.com
Date: Tue, 15 Feb 94 18:53 PST
Message-id: <199402160237.SAA23691@cory.EECS.Berkeley.EDU>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: "John D. Mitchell" <johnm@cory.EECS.Berkeley.EDU>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Beginner questions
Status: OR
Hmm...  I seem to have missed the start of this thread but anyways...

Blocks should be locked only when the are being actively accessed.
Fiddling about trying to outguess the system as far as when to move blocks
and what not isn't all that useful.  The system has been designed to be as
fast as possible in efficiently locking and unlocking blocks.

When you get your application/library debugged and ready to ship then spend
some time using the various profiling stuff (in analysis.tcl) and thinking
hard about what you've found out.  At that point, there's all sorts of
things that you can do that can make a huge difference in the performance
of your code.  Premature optimization is a Bad Thing.

John "GEOS Mercenary" Mitchell