You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2007/01/30 08:19:38 UTC
optimizing serialized state: optimizing component
yet another brainstorm on the subject
a big percentage of components do not have
metadata/behaviors/markupattributes/markupindex/etc, but we always write
them out (even if null). what if we allocate a few more component flags and
use custom serialization to not write those out based on flags. this should
really shrink serialized size of components. the above will save 4 slots per
component! on a page with a datatable that will really add up.
-igor
Re: optimizing serialized state: optimizing component
Posted by Igor Vaynberg <ig...@gmail.com>.
right, these are just guesses, nothing certain.
-igor
On 1/30/07, Johan Compagner <jc...@gmail.com> wrote:
>
> So make those things all transient?
> and then do readDefault()/writeDefault() and then read in the things that
> could be null
>
> again lets do it and look what it saves us.
>
>
> On 1/30/07, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > yet another brainstorm on the subject
> >
> > a big percentage of components do not have
> > metadata/behaviors/markupattributes/markupindex/etc, but we always write
> > them out (even if null). what if we allocate a few more component flags
> > and
> > use custom serialization to not write those out based on flags. this
> > should
> > really shrink serialized size of components. the above will save 4 slots
> > per
> > component! on a page with a datatable that will really add up.
> >
> > -igor
> >
> >
>
>
Re: optimizing serialized state: optimizing component
Posted by Johan Compagner <jc...@gmail.com>.
So make those things all transient?
and then do readDefault()/writeDefault() and then read in the things that
could be null
again lets do it and look what it saves us.
On 1/30/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> yet another brainstorm on the subject
>
> a big percentage of components do not have
> metadata/behaviors/markupattributes/markupindex/etc, but we always write
> them out (even if null). what if we allocate a few more component flags
> and
> use custom serialization to not write those out based on flags. this
> should
> really shrink serialized size of components. the above will save 4 slots
> per
> component! on a page with a datatable that will really add up.
>
> -igor
>
>