Andrey,

Other types will have lazy initialization, it's a default behavior.

Evgenii

вт, 2 окт. 2018 г. в 18:02, Andrey Davydov <[email protected]>:

> Will binary serialization work for all other classes not listed in
> typeConfiguration?
>
>
>
> Andrey.
>
>
>
> *От: *Evgenii Zhuravlev <[email protected]>
> *Отправлено: *2 октября 2018 г. в 16:14
> *Кому: *[email protected]
> *Тема: *Re: Binary marshaller warm up
>
>
>
> Hi,
>
>
>
> You can try to config BinaryConfiguration.setTypeConfigurations, it will
> work like pre-defined types.
>
>
>
> Evgenii
>
>
>
> вт, 2 окт. 2018 г. в 14:58, Andrey Davydov <[email protected]>:
>
> Hello.
>
>
>
> There is difficult transaction in my system, requires to put about 50
> objects to 7 different ignite caches. Objects have 7 different classes.
> Some of them have difficult internal structure with object and collection
> fileds.
>
>
>
> The first execution of this transaction after empty cluster startup takes
> about 500-700 ms. All other executions of exactly same transaction take
> 10-20 ms.
>
>
>
> I think it is due to cluster wide initialization of binary marshaller
> metadata (seems too long for class loading).
>
>
>
> If there is any way to initialize marshaller with list of required classes
> on startup?
>
>
>
> Andrey.
>
>
>
>
>

Reply via email to