There is a data context (I will not give it) and I have such an adapter

public class Adapter { FilmsContext _filmsContext; public IEnumerable<Film> Getfilms() { return _filmsContext.Films; } }

And that's when I request the first movie.

 var films = adapter.Getfilms(); var film = films.First();

Data acquisition takes about 3 seconds. In table 4 entries. A SELECT TOP 1 query ... followed by parsing is almost instantaneous. Of course, I understand that EF imposes some inconvenience in terms of speed, but not so much. Maybe you need to configure it somehow?

  • Well, here we are. In your other question, I suggested that all these heavy juggles are not for SQLite. - Bulson
  • @Bulson, for some reason it seems to me that you are wrong. - iRumba
  • PROFILE. Well, for garbage, you did not bring any information, request for 3 seconds, guess what is wrong. In my sqlite gig base, there is also a healthy ORM on top and there are no such long queries. - Monk
  • But not, all the rules, only the first request is executed for a long time - iRumba
  • @Monk, do not swear you, I am far from you in terms of working with the database and database. First, as it turned out, this is the first request that takes a long time (apparently forming a request, etc.), and secondly, the word “PROFILE” says little to me. I would have an algorithm of actions in such cases. - iRumba

0