> I've never done speed or memory comparisons between serp and ASM,
> but I
> wouldn't be surprised if they're in the same ballpark for
> general-purpose usage. Anyone have any knowledge about ASM's
> speed / mem
> consumption?
Though I haven't used it, based on its architecture I would guess
that ASM is significantly faster and less memory-hungry. However,
given that:
- Our code using serp works.
- It's easier to work with serp.
- Performance is not of primary concern at dev time.
- The cost of the little runtime bytecode processing we do is
amortized over the life of the app.
I would put an "upgrade" to ASM way, way down on any OpenJPA TODO list.
If you're interested in bytecode processing, Patrick, Marc, and I
were just discussing a bytecode-related project we'd really like to
see someone work on once OpenJPA stabilizes...
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
|