Databases
StackOverflow2013
Postsdbo
POEntity Framework consuming a lot of memory (possible memory leak?)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEntity Framework consuming a lot of memory (possible memory leak?)
    primarykey
    data
    text
    <p>We are using EF4.3.1 in a WCF service ( our business \ application layer). We are using EF Code First with existing database and Fluent Mapping (EntityTypeConfiguraiton). An instance of DbContext is created for each request and then disposed off. </p> <p>We have a generic repository which uses the DbContext. </p> <p>When running on test servers we found that the Business layer app pool is going out of memory in 30 mins or so with 10 concurrent users. We took dump of the IIS worker process and found that EF is consuming a lot of memory, there were many object in on large object heap created by EF. We could see objects for data retrieved from th DB on the heap. Not sure if the DbContext dispose is taking care of this. The % time in GC was very high (> 16%). One strange thing we noticed in the dump file was, there was a huge string object (around 87MB) storing string representation of all my mapping files. I found this to be very strange,</p> <p>Has anybody encountered any such memory leak issue with EF? Also please also let us know if there is something wrong in our usage of EF. Please let me know if more details are required.</p> <p>Thanks Prasad</p> <p><strong>EDIT</strong> We inject an instance of DbContext using AutiFac DI (WCF integration). The life time for Dbcontext is InstancePerLifeTime ( one request per http request). We have implemented this way to share the instance of DbContext in all repositories instances in one HTTPrequest.</p> <p>The way we access database is // declaration IGenericRepository UserRepository {get;set;} // Property injection using AutoFac</p> <p>// Usage var user = UserRepository.FindBy(u => u.userid == "test@test.com");</p> <p>We are not using explicit transactions in repositories. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPrasad
    1. USPrasad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. USSlauma
      1. VTFavorite
    1. COCould you shows us example of how you're using some transaction with EF?
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. USJorge
    2. CO@Jorge , please find the EDIT to the original question.
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. USPrasad
    3. COWe did some analysis on this, it appears operations like Sum \ Average through one to many relations causes slowness. We moved some of these operations to the stored procs and the performance improved. This also reduced memory pressure, we are still fine tuning will add comments based on our findings
      singulars
      1. POEntity Framework consuming a lot of memory (possible memory leak?)
      1. USPrasad
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload