Right now the getAt(index) methods works also for Records, but creates a new RecordView object every time. For Records allow only the overloaded version of the method where a reusable view is given -> getAt(index, reuse).
With the help of Inlining and Escape Analysis the performance impact might be reducable. But right now the Records.view(blueprintId, recordId) method is to complex.
http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html#escapeAnalysis
Right now the getAt(index) methods works also for Records, but creates a new RecordView object every time. For Records allow only the overloaded version of the method where a reusable view is given -> getAt(index, reuse).
With the help of Inlining and Escape Analysis the performance impact might be reducable. But right now the Records.view(blueprintId, recordId) method is to complex.
http://docs.oracle.com/javase/7/docs/technotes/guides/vm/performance-enhancements-7.html#escapeAnalysis