Super Fast Object Cloner / Allocator with No Constructor and Initialize Overhead by Cloning from a Given Template Object Which was Previously Allocated

[sirinath]

Running the constructor logic and initializers take cycles. Is it possible to have a safe fast clone which only retains side effects. (Mainly static field updated I think.)

[sirinath]

I hope this is the right place to open the issue. It is good to have something like this in one of the projects.

[peter-lawrey]

Can you give an example of what you mean? The fastest approach is to not
copy the data at all and use it in place. i.e. while still off-heap.

On 11 June 2014 14:19, Suminda Dharmasena notifications@github.com wrote:

Running the constructor logic and initializers take cycles. Is it possible
to have a safe fast clone which only retains side effects. (Mainly static
field updated I think.)

—
Reply to this email directly or view it on GitHub
#43.

[peter-lawrey]

We have support for off heap references to data structures using interfaces
as a template. Can you give an example of what you mean?

On 11 June 2014 14:21, Suminda Dharmasena notifications@github.com wrote:

I hope this is the right place to open the issue. It is good to have
something like this in one of the projects.

—
Reply to this email directly or view it on GitHub
#43 (comment).

[sirinath]

When I create an Object the initializers run and the Constructor is called. If the constructor does the same initialization e.g. the NoArg constructor. No need to have this run always. Any new object created will be of the same state. So store this state can just copy it when you need a new object.

I am looking for both On Heap (if fall back to GC is not available) and Off Heap.

Basically custom allocator which acts like the new operator but faster than the default behaviour of new by remembering the previous effects of object creation.

[peter-lawrey]

For an off heap clone you can copy the raw Bytes. For on heap you would
need a static factory for new objects and this could clone a prebuilt
instance.
On 11/06/2014 7:04 PM, "Suminda Dharmasena" notifications@github.com
wrote:

When I create an Object the initializers run and the Constructor is
called. If the constructor does the same initialization e.g. the NoArg
constructor. No need to have this run always. Any new object created will
be of the same state. So store this state can just copy it when you need a
new object.

I am looking for both On Heap (if fall back to GC is not available) and
Off Heap.

—
Reply to this email directly or view it on GitHub
#43 (comment).

[sirinath]

Is it possible to add an easy API around this?

[sirinath]

Say I want to stamp out 10 objects but have the constructor and initiation logic to run only once and also be able to stamp out new version for the internally maintained template on demand. (Internal template object should be protected so the state is as if it would be just after creation.) Also if I already have an object stamp out new clones from it. If there is some side effects in the constructor just a pure copy will not work. May be you can add something to do this later on.

Should be well tested on OpenHFT Collection, GS Collections, Guava and Java Collections also there you can just do a low overhead duplication / cloning.

[peter-lawrey]

Roman, can you review this?

[leventov]

I don't think this is relevant anymore.