This commit is contained in:
@@ -17,10 +17,6 @@ Prioritize items to get to beta fast as possible
|
||||
|
||||
|
||||
|
||||
todo: huge data erasedatabase to reseed failing with timeout on aunit delete due to requiring indexes
|
||||
added the indexes, now need to re-test: genhuge over lunch or something will take 30 minutes
|
||||
|
||||
|
||||
//performance overall sanity check before beta release
|
||||
|
||||
hotspots or potential ones in small sample generation:
|
||||
@@ -44,6 +40,15 @@ SEEDING PERF LEVELS:
|
||||
2021-10-20 11:46:06.5739|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 26 seconds
|
||||
2021-10-20 13:30:27.4610|INFO|Seeder|HUGE level sample data seeded in 34 minutes and 10 seconds
|
||||
|
||||
Installed PG server:
|
||||
2021-10-20 14:42:17.8716|INFO|Seeder|Small level sample data seeded in 15 seconds
|
||||
2021-10-20 14:45:17.1372|INFO|Seeder|MEDIUM level sample data seeded in 2 minutes and 2 seconds
|
||||
2021-10-20 14:54:46.5645|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 19 seconds
|
||||
2021-10-20 15:38:00.4839|INFO|Seeder|HUGE level sample data seeded in 38 minutes and 27 seconds
|
||||
slower??
|
||||
Trying again with standalone pg....
|
||||
|
||||
|
||||
|
||||
|
||||
-------------------------------------
|
||||
@@ -57,11 +62,8 @@ todo: hard cap on appointments brought back controlled by client in settings oth
|
||||
todo: hard cap timeout on anything very time consuming like report generation, datalist queries, schedule etc
|
||||
if a report ties up the server for more than XX seconds it should stop it adn return an error too big
|
||||
|
||||
todo: server metrics broken?
|
||||
nope, not sure why I saw this, maybe it doesn't capture during a huge generate??
|
||||
|
||||
todo: profile the server during seeding, it's unbelievably slow, what exactly is the slowness caused by and what can be done to fix it?
|
||||
https://github.com/Microsoft/perfview
|
||||
|
||||
|
||||
|
||||
todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues?
|
||||
|
||||
Reference in New Issue
Block a user