Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
From: Andrus Adamchik <andrus@objectstyle.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Cayenne object storage / memory usage
Date: Fri, 9 Jun 2017 22:41:41 +0300
References: <CAOUwSGuNmQQgs+aG=pb_qxnCz6yxm-_McfOfiUYYw3Eq2gg6Dg@mail.gmail.com>
 <189FE6CA-66F9-4FA1-8415-6A90D52C3748@objectstyle.org>
 <CAOUwSGu4g57GeXsgLjtuCW2pFRBUVge=fOueEd3XhjFyh7kOMQ@mail.gmail.com>
To: dev@cayenne.apache.org
In-Reply-To: <CAOUwSGu4g57GeXsgLjtuCW2pFRBUVge=fOueEd3XhjFyh7kOMQ@mail.gmail.com>
Message-Id: <4A015B64-C396-45F4-975A-DA01F6CF554A@objectstyle.org>
archived-at: Fri, 09 Jun 2017 19:41:50 -0000


> On Jun 9, 2017, at 9:29 PM, John Huss <johnthuss@gmail.com> wrote:
>=20
>>> I can't imagine a more efficient representation that fields.
>>=20
>> True, but fields also require reflection to be accessed "from below" =
(by
>> Cayenne).
>=20
>=20
> It doesn't have to use reflection. With Java 7 and newer you can use
> strings in switch statements with a single jump, which is what I'm =
doing.
> The class template generates the readPropertyDirectly method with the
> switch statement in it.  This is both fast and simple.  Also, using =
fields
> makes it much easier to inspect your objects in the debugger, which is
> handy.

Yeah, using fields would be great. It is certainly much more =
developer-friendly. I'd like to run some benchmarks on "switch", but =
this may be a quick way for us to improve the framework without =
rewriting the stack.

The only potential advantage of an Object[] approach would be the =
ability to replace object state atomically. Maybe someday we'll be able =
to take advantage of that. But at the moment what you are suggesting =
looks very promising and also "easy".

Andrus