what are the design constraints a user has to consider.
Currently, #process(Entity) becomes private (there seems to be a slight perf gain from invoking it as a private method, presumably the JVM can omit de-optimization guards in the generated assembly).
It will however be fixed before the issue is closed, probably with an annotation of some sort: so if one needs to invoke #process from an external class, it should be possible to control.
Also, doesn't work from the CLI tool yet, but it's coming.
android compatibility/benefits.
Compatible, though I haven't tested it. Not sure how aggressively dalvik JITs stuff or how it does its method dispatch. I'd like to think it'd improve performance, but needs testing.
Any other weaving goodness currently not advertised?
Nope, apart from making this work with GWT too, but it's further down the line. @PackedWeaver can likely be optimized without relying on bytecode manipulation.
junkdog
commented
9 years ago
Cut this out of the https://github.com/junkdog/artemis-odb/wiki/Hotspot-Optimization page as it doesn't seem current. Please take a quick look to see if any of it is still relevant.
Currently,
#process(Entity)becomes private (there seems to be a slight perf gain from invoking it as a private method, presumably the JVM can omit de-optimization guards in the generated assembly).It will however be fixed before the issue is closed, probably with an annotation of some sort: so if one needs to invoke
#processfrom an external class, it should be possible to control.Also, doesn't work from the CLI tool yet, but it's coming.
Compatible, though I haven't tested it. Not sure how aggressively dalvik JITs stuff or how it does its method dispatch. I'd like to think it'd improve performance, but needs testing.
Nope, apart from making this work with GWT too, but it's further down the line.
@PackedWeavercan likely be optimized without relying on bytecode manipulation.