|
I have a performance and functionality question
regarding org.exolab.castor.persist.addObjectEntry and org.exolab.castor.persist.removeObjectEntry methods.
I was doing
some profiling and I noticed that I was spending a lot of time in these two
functions. It was cycling through the entire '_objects' vector for lookups. Is
there any reason why it can't be a HashMap or Hashtable? I added
_objectsLookup Hashtable for getObjectEntry and I got a significant performance
improvement for getObjectEntry.
Does the create function need the objects
collection to ordered.
Steve |
