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
There are a lot of reflections / dynamic object allocations / boxing operations. This seems inappropriate for many "real-time" systems (is that a goal or does that just happen to be the company name?)
It does not seem to address schema evolution, but I might have missed something
: True.
Lots of if / else-if checks for checking sequential integers? Why not use a switch?
: Expecting somewhat low-level optimizer will work on this.
The used big-endian encoding is more difficult to be optimized later on
The text was updated successfully, but these errors were encountered:
Check the link below
https://www.reddit.com/r/java/comments/u4ytxu/github_realtimetechsolutionopack_fast_object_or/
There are a lot of reflections / dynamic object allocations / boxing operations. This seems inappropriate for many "real-time" systems (is that a goal or does that just happen to be the company name?)
It does not seem to address schema evolution, but I might have missed something
: True.
Lots of if / else-if checks for checking sequential integers? Why not use a switch?
: Expecting somewhat low-level optimizer will work on this.
The used big-endian encoding is more difficult to be optimized later on
The text was updated successfully, but these errors were encountered: