This commit is contained in:
@@ -15,6 +15,25 @@ After round one of improvements (less text in seed data notes, not calling savec
|
||||
2020-01-23 16:57:57.0422|INFO|Seeder|75 Users seeded in 2398 ms
|
||||
2020-01-23 16:58:11.9983|INFO|Seeder|500 Widgets seeded in 14958 ms
|
||||
|
||||
TODO: Find out if this is linear time for more widgets or exponential to see if it exposes part of the issue
|
||||
X widgets, ms per widget:
|
||||
100=32
|
||||
500=29 (27 in non debug mode)
|
||||
5000=29
|
||||
|
||||
|
||||
Stripped out all text to index except single letter a in notes and c2
|
||||
500=20
|
||||
|
||||
Now going to try the opposite, a *lot* of text 10 paragraphs in both c2 and notes
|
||||
500=59ms
|
||||
|
||||
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
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user