[squeak-dev] OmniBase/Magma - how big??

Chris Muller asqueaker at gmail.com
Sat Mar 1 04:58:02 UTC 2008


>  IMHO I think Magma would SHINE if we somehow could boost the
>  serialization/deserialization mechanism in it. Because I suspect this is
>  where the bottleneck is regarding the above. An Exuperified Magma could
>  be the answer - or some other HARD approach - I dunno. Chris?

Magma users will appreciate the new r41Beta1 just posted Wednesday.
Profiling had shown Magma spending quite a bit of time in
IdentityDictionary's, largely for oid lookups.  I'm still
benchmarking, but with Igors new IdentityDictionary replacements I am
seeing tremendous gains across the board, for both reads and commits.

I'm also excited for single-clause Readers now improved #size and #at:
by a factor of 100x.. again!  They're so fast now, as a joke, I
demonstrated a scrolling list with more than two-hundred thousand
objects (two million would work as well)  The list widget only needs
its underlying domain to understand #size and #at:, so the Reader
plugs-in seamlessly.  Scrolling performance is good, even with remote
connections.



More information about the Squeak-dev mailing list