logoalt Hacker News

tilneyesterday at 12:50 AM2 repliesview on HN

Doesn’t entity framework have a huge memory footprint too?


Replies

homebreweryesterday at 10:47 AM

If you don't do stupid things like requesting everything from the database and then filtering data client side, then no.

We have one application built on .NET 8 (and contemporary EF) with about 2000 tables, and its memory usage is okay. The one problem it has is startup time: EF takes about a minute of 100% CPU load to initialize on every application restart, before it passes execution to the rest of your program. Maybe it is solvable, maybe not, I haven't yet had the time to look into it.

show 2 replies
neonsunsetyesterday at 1:07 AM

Do you have any links that note memory usage issues with any of the semi-recent EF Core versions?

show 1 reply