We do not provide official documents on the topic so far. We are considering at the moment whether to provide such on a company level. What I'm authorized to share so far is that we have similar performance to EntityFramework in most cases and are faster that some of the other vendors. Also you have to know that Plain ADO.NET (as expected) has the best performance, it is just that you have to maintain a lot of code that is usually not very portable and maintainable. My suggestion is:
If you are very dependable on performance (and the maintenance cost is of no importance), maybe you should go with ADO.NET and forget about O/R mappers. Actually we do provide optimizations like L2 cache and fetch optimizations, but nevertheless there will be a small performance overhead always compared to ADO.NET (I assume that we compare an optimal ado.net implementation).
In all other cases I suggest that you take the time and make a sample/spike with OpenAccess to see some specifics whether it works for you. We can guide you through the process as we provide support even for the trial downloads.
Hope that helps with your decision. Do not hesitate to contact me further.
the Telerik team
, the state of the art learning tool for Telerik products.