Ok. I read your paper. It always feels good to know about the efforts that underlie a working system. Especially, the emphasis on a formal approach to ensure a lossless roundtrip. I suggest that you put a link to this paper somewhere that more people may see it and better appreciate the system they use.
BTW, as I responded to your blog post, I've been unable to generate views (we building EF6 an use it), so I still need to improve my speed. I have two suggestions:
- Allowing some kind of runtime view generation without checking the roundtrip condition (It is implied from the paper that it takes most of the view generation time). Most of our developer work does not include changing the model. Even when they do change the model, most of their work is about adding a simple property, or a very simple table. It was great if we could disable this, and have a nightly, or hourly job make sure the view is in good conditions. In other words, roundtrip condition checking be removed from every first run of the application and delegated to the development team (trust us, we can handle such a task!)
- I profiled the view generation, and 81% of the time was spent in ViewGenContext.CreateConstraintsForForeignKeyAssociationsAffectingThisWarapper(). Most of the time elapsed in this code is spent in Enumerating an IEnumerable, obtained by filtering EdmEntityContainer.BaseEntitySets. The moral of this for me is that a simple ReadOnlyCollection is not appropriate to keep this data, and a better data structure will yield a 5X speed boost. Fortunately, this collection is not used in many places among the code and I'll be able to understand all queries we perform on the list. I'll inform you if any improvements are made.