view vs getindex performance

I was replacing AxisArrays with ComponentArrays in a package (MuJoCo.jl) since AxisArrays kills the initial compile time despite having excellent run-time performance. ComponentArrays has a compatible interface that doesn't break user's code, but there are performance differences when using getindex:

As you can see, doing the getindex style access of the ComponentArray is much slower than the view, although from the source code I can't exactly tell why that would be the case since they should both be converting to Vals (which seems to be the slowdown). For some reason the conversion toval doesn't happen at compile-time for getindex could explain the slow-down?

While I can access the data as a property q.slider that doesn't work for multi-dimensional ComponentArrays which we have. I'll put a note in our docs about this, but was wondering if you had any insights as to what's going on. Thanks!

Begin by comparing the ComponentArray getindex and view entry points and reproduce the access timings described in the issue. Done means explaining or correcting the conversion-to-Val performance difference, with updated behavior or guidance for multidimensional access.