"adrian(a)jboss.org" wrote : "jason.greene(a)jboss.com" wrote : and it can
do direct method invocation as opposed to reflection which is definitely faster.
| I think you'll find that that is probably not as relevant as you think.
| This is a similar problem to Serialization.
| The time it takes to
| 1) decide what to do - typically a string comparison on an element or attribute name
| 2) coerce xml data into non-string types
| will likely "swamp" the small amount of extra time it takes to invoke a
setter via reflection,
| most of which is the construction of an Object array to pass to Method.invoke().
| That's not to say the difference is unimportant.
| If you have to parse lots of xml, it will definitely add up over time.
Yes you have a point, it may not be that faster for one parse. However, reflection does
involve all kinds of initial caching on the first invocation, so maybe it will have some
small but measurable impact. It should definitely not be slower though which is really
what i was driving at.
anonymous wrote :
| e.g. See my 0.4 seconds from 2.4 seconds estimate above (which is probably not
| all reflection overhead anyway?)
Right, the binding is really what I was thinking would be the actual area to improve on.
You are definitely correct that with only 30% of the time being binding we may be
disappointed. However, I suspect that the parsing time portion of the pie is off because
of schema validation. That is known to be slow. We should try disabling that and see what
View the original post :
Reply to the post :