An MC challenge: As a practical matter what size package is
best when using MC.
cputney at wiresong.ca
Sun Aug 27 05:59:37 UTC 2006
On Aug 27, 2006, at 1:30 AM, Peace Jerome wrote:
> So I am of the learning that MC
> does (or at least didn't) scale well.
> On what scale does it work admirably.
> On what scales does it fail to work well?
You're right, Monticello doesn't scale well.
However, your questions are impossible to answer. It depends on how
fast your machine is, how much memory it has, how fast your net
connection is (if you're using a remote server), how fast the server
is, what your personal tolerance for UI responsiveness is, and what
version of Monticello you're using.
You might also be affected by particularly high tides, proximity high
tension power lines, and the amount of walrus blubber in your diet.
Seriously, the biggest factor is probably the combined number of
classes and methods in your packages. If you can keep your packages
from getting too big, it should work fine. Note that breaking large
packages into several smaller packages should improve things. It also
helps if you make small, frequent commits, rather than bunching up
lots of changes into a single commit.
Hope this helps,
More information about the Squeak-dev