This commit is contained in:
@@ -48,12 +48,18 @@ Async the keyword processing
|
||||
|
||||
Removing use of EF entirely in search indexing processing in favor of direct sql queries
|
||||
|
||||
cache or provide directly the locale to save time repeatedly fetching it when doing bulk ops
|
||||
cache or provide directly the locale to save time repeatedly fetching it when doing bulk ops!!!
|
||||
-After doing this 500=21 That's as fast as when I stripped out all the text, what a huge overhead saving right there!:
|
||||
2020-01-24 12:00:41.2547|INFO|Seeder|Seeding 500 Widgets....
|
||||
2020-01-24 12:00:51.9138|INFO|Seeder|500 Widgets seeded in 10649 ms
|
||||
|
||||
///////////////////////////////////////////////////////////////////////////////
|
||||
|
||||
|
||||
|
||||
TODO: Locale search data, there is overhead on every record save due to having to repeatedly fetch this
|
||||
- While I added a way to seed it without fetching, there should actually just be a cached version for all record saving stored locally
|
||||
- Fetches in the db are not necessary for this object more than once or on change of locale
|
||||
- So probably Search code should cache it internally on first fetch
|
||||
|
||||
TODO: RUN data list query with debug info on and see if any EF stuff is creeping into it
|
||||
|
||||
|
||||
Reference in New Issue
Block a user