admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-10-19 17:54:48 +00:00
parent 05adcdbe44
commit 8b25bd4856
1 changed files with 18 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
ayanova/devdocs/todo.txt
View File

@@ -15,19 +15,25 @@ Prioritize items to get to beta fast as possible
make an official to beta list of items and even if others are there they can wait make an official to beta list of items and even if others are there they can wait
//performance overall sanity check before beta release //performance overall sanity check before beta release
build a release windows build
run it outside vstudio
use dotnet-trace ps to find it's id
trace it and then generate sample data
stop tracing adn veiw the trace in perfview
find hotspots
$profit
https://docs.microsoft.com/en-us/aspnet/core/performance/performance-best-practices?view=aspnetcore-5.0
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace
hotspots or potential ones in small sample generation:
updatetagsinrepository seems slower than search index!?
6.00s (22%) 5.52ns (<0.01%) AyaNova!AyaNova.Biz.TagBiz+<ProcessUpdateTagsInRepositoryAsync>d__5.MoveNext()
log job / log status async during seeding
unitbiz.validateasync MOVE NEXT??
UnitBiz keeps coming up in several threads weirdly, it seems to trigger things all over the place, is it heavier than most in some way??
24.28s (91%) 172.03ns (<0.01%) Npgsql!Npgsql.Internal.NpgsqlReadBuffer+<<Ensure>g__EnsureLong|41_0>d.MoveNext()
AyaNova!AyaNova.Biz.EventLogProcessor+<LogEventToDatabaseAsync>d__1.MoveNext() comes up a lot too, event logging maybe could be improved??
Get job status from client checking repeatedly on seeding
should change this to check less frequently
todo: perf, test installed postgres vs standalone jimmied one for same op
todo: hard cap on appointments brought back controlled by client in settings otherwise unusable todo: hard cap on appointments brought back controlled by client in settings otherwise unusable
ideally centered around current date ideally centered around current date
@@ -401,6 +407,8 @@ todo:1.5 Joyce case 3931 test restore of 4alarm data
make sure it works one way or another make sure it works one way or another
confirm it's really backing up everything confirm it's really backing up everything
todo: 1 api root page should should license info
todo: 2 make priority / woitem / wostatus colors distinct from each other todo: 2 make priority / woitem / wostatus colors distinct from each other
whitecaps color scheme shale/pastel etc whitecaps color scheme shale/pastel etc
Note: wostatus will be the default color source so concentrate on making that look nice and clean Note: wostatus will be the default color source so concentrate on making that look nice and clean