[squeak-dev] OmniBase/Magma - how big??
Sebastian Sastre
ssastre at seaswork.com
Sat Mar 1 14:56:22 UTC 2008
Great new Crhis. Great news
thanks for that
Sebastian Sastre
> -----Mensaje original-----
> De: squeak-dev-bounces at lists.squeakfoundation.org
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] En
> nombre de Chris Muller
> Enviado el: Sábado, 01 de Marzo de 2008 01:58
> Para: The general-purpose Squeak developers list
> CC: magma at lists.squeakfoundation.org
> Asunto: Re: [squeak-dev] OmniBase/Magma - how big??
>
> > 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
|