In the context of maintaining squeak as packages:

-What is the largest practical package to store (and
load) as an MC package.

-What is the smallest practical package to store
separately (and load) as an MC package.

You can name whatever parameter for size that you
want.
(Bytes, Classes, Messages, Or Class>>Methods )

The practical aspect is in terms of resources.
Programmer time mostly. But this is affected by how
much memory the image has to have allocated to it to
successfully load the package. 

I early on tried to save Morphic as a package (even
before it was split) with time consuming and then
disastorous results. (My iMac has about 100M allocated
to squeak.) Even maxing out the allocation ( which for
my resources stopped at ~200M) just used up more time
for no greater result. 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?


Yours in curiosity, -- Jerome Peace



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com