I'm struggling to find any concrete performance of Entity Framework paired with SQL server 2012.
We're looking at storing nearly a million points in a database an right now the most common scenario would be to find all points within radius of N.
I've mocked up a small prototype using EF5 and it seems fine. However, a senior developer has mentioned that in his opinion EF is bloated and I should consider using a micro-orm or even pure ADO.NET as EF is a bloated monster (lol).
Performance is crucial on this project and I would like to know if anyone has experience to prove this guy otherwise (or right for that matter)?