You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking at optimising my use of Xodus and realised calls to getProperty() can be quite expensive.
In my case, I am indexing the properties of files. In this case, the file locations are static and could be used as identifiers.
For entities where we have some identifier which we can guarantee to be unique, would it be worth allowing the client to specify their own getLocalId()?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been looking at optimising my use of Xodus and realised calls to
getProperty()
can be quite expensive.In my case, I am indexing the properties of files. In this case, the file locations are static and could be used as identifiers.
For entities where we have some identifier which we can guarantee to be unique, would it be worth allowing the client to specify their own
getLocalId()
?This way, it's one less
getProperty()
call...Beta Was this translation helpful? Give feedback.
All reactions