devdocs/todo.txt

@@ -5,7 +5,13 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ
 
 ## IMMEDIATE ITEMS
 
-PERFORMANCE WORK
+///////////////////////////////////////////////////////////////////////////////
+TODO: Search indexing is painfully slow, it accounts for 16 of 22 seconds when creating 500 widgets with full paragraphs of text 
+	- Try to see if it's just one part of the operation by timing it
+	- Re-code it not using EF but directly interacting with the DB
+	- Maybe it's a case for stored procedures or something?
+
+SEARCH INDEXING PERFORMANCE WORK
 Baseline from before doing anything seeding a medium level with full text
 2020-01-21 16:49:17.4662|INFO|Seeder|75 Users seeded in 2279 ms
 2020-01-21 16:49:39.4481|INFO|Seeder|500 Widgets seeded in 21968 ms
@@ -30,16 +36,26 @@ Now going to try the opposite, a *lot* of text 10 paragraphs in both c2 and note
 
 So the quantity of text directly affects the performance, so it's not just some overhead from the query being run, it's the amount of work it needs to do in the queries
 
+THINGS TO TRY:
+Completely alternate methods:
+	- https://stackoverflow.com/a/15089664/8939  Store a Digest of each record with that record then can just search the digests (would mean a search has to traverse all records of every table possibly)
+
+DB INDEX TUNING?
+	- Play with the indexes and see if there is a slowup with an unnecessary index maybe affecting things
+
+Async the keyword processing
+	- Fire off the indexing and return immediately so there would be a bit of time to come into compliance maybe more clashes?
+
+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
+
+///////////////////////////////////////////////////////////////////////////////
 
 
 
 
-TODO: Search indexing is painfully slow, it accounts for 16 of 22 seconds when creating 500 widgets with full paragraphs of text 
-	- Try to see if it's just one part of the operation by timing it
-	- Re-code it not using EF but directly interacting with the DB
-	- Maybe it's a case for stored procedures or something?
-
-
+TODO: RUN data list query with debug info on and see if any EF stuff is creeping into it
 
 
 TODO: DataFilter how to distinguish between filtering on specific ID value or on value column