Databases
StackOverflow2013
Postsdbo
POEntity framework transfer thousands of objects to Elastic Search
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEntity framework transfer thousands of objects to Elastic Search
    primarykey
    data
    text
    <p>I am creating a web app that will have a database on every town, region and country in the world to allow for mapping other objects to a location. As part of the application I want the users to be able to search for a place, to do this I am using Elastic Search to index everything. To interact with Elastic Search I am using NEST.</p> <p>I have the following code:</p> <pre><code>public void RefreshLocationIndex() { int count; using (var dbContext = new ModelContext()) { IndexMany(dbContext.Countries, "Country"); } using (var dbContext = new ModelContext()) { count = dbContext.Regions.AsNoTracking().Count(); } for (var i = 0; i &lt;= count; i += BATCH_SIZE) { using (var innerContext = new ModelContext()) { IndexMany(innerContext.Regions.OrderBy(t =&gt; t.RegionID).Skip(i).Take(BATCH_SIZE), "Region"); } } using (var dbContext = new ModelContext()) { count = dbContext.Towns.AsNoTracking().Count(); } for (var i = 0; i &lt;= count; i += BATCH_SIZE) { using (var innerContext = new ModelContext()) { IndexMany(innerContext.Towns.AsNoTracking().OrderBy(t =&gt; t.TownID).Skip(i).Take(BATCH_SIZE), "Town"); } } } public void IndexMany(IQueryable&lt;Entity&gt; objects, string type) { var itemCount = objects.Count(); if (itemCount &gt; 0) { SearchClient.Instance.IndexManyAsync(objects, SearchClient.Instance.Settings.DefaultIndex, type); } } </code></pre> <p>As you can see I am separating the very large tables into batches to try to avoid loading to much into memory. The problem is this is not working, and I keep getting out of memory exceptions. I thought that using a new context for each batch would avoid this issue as when the context was disposed it would dispose of all the entities it had loaded, this doesn't seem to be the case. Any ideas?</p> <p>Just as an indication of the amount of data: Country table has 193 records Region table has 80,523 records Town table has 2,743,469 records</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMike Norgate
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEntity framework transfer thousands of objects to Elastic Search
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEntity framework transfer thousands of objects to Elastic Search
      1. USMike Norgate
      1. VTBountyStart
    3. VO
      singulars
      1. POEntity framework transfer thousands of objects to Elastic Search
      1. This table or related slice is empty.
      1. VTUpMod
    1. COis it wise to create and dispose your big dbcontext 80,523 times for only region and 2,743,469 for towns?
      singulars
      1. POEntity framework transfer thousands of objects to Elastic Search
      1. USVishal Sharma
    2. COyou need to wait for IndexManyAsync to finish adderwise you put everything in memory while you wait for it to complete.
      singulars
      1. POEntity framework transfer thousands of objects to Elastic Search
      1. USPedro.The.Kid
 

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