This commit is contained in:
@@ -11,25 +11,11 @@
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
todo: auth when server locked, who can login when?
|
Prioritize items to get to beta fast as possible
|
||||||
Super user can *always* login??
|
make an official to beta list of items and even if others are there they can wait
|
||||||
|
|
||||||
|
|
||||||
|
//performance overall sanity check before beta release
|
||||||
TODO: SEEDER
|
|
||||||
- generate LESS PM's, a finite amount, otherwise there are so many the server is constantly generating after seeding
|
|
||||||
- bugbug, can't login as superuser when activeuser count is exceeded
|
|
||||||
also, seeder allowed exceeding active user count
|
|
||||||
up the trial user count
|
|
||||||
allow login of superuser only when active count exceeded as the error message suggests should work
|
|
||||||
attempt to delete a user to free up license but got error:
|
|
||||||
update or delete on table "auser" violates foreign key constraint "aworkorderstate_userid_fkey" on table "aworkorderstate"
|
|
||||||
so apparently they don't affect history when update workorderstate
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
//performance
|
|
||||||
build a release windows build
|
build a release windows build
|
||||||
run it outside vstudio
|
run it outside vstudio
|
||||||
use dotnet-trace ps to find it's id
|
use dotnet-trace ps to find it's id
|
||||||
@@ -41,6 +27,8 @@ $profit
|
|||||||
https://docs.microsoft.com/en-us/aspnet/core/performance/performance-best-practices?view=aspnetcore-5.0
|
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
|
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
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
|
||||||
applies to month view
|
applies to month view
|
||||||
@@ -50,6 +38,7 @@ todo: hard cap timeout on anything very time consuming like report generation, d
|
|||||||
if a report ties up the server for more than XX seconds it should stop it adn return an error too big
|
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?
|
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?
|
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
|
https://github.com/Microsoft/perfview
|
||||||
@@ -236,6 +225,9 @@ function ayGroupByTag(reportDataArray, tagContains) {
|
|||||||
confirm the filter in datatable matches what is really happening on login and access etc
|
confirm the filter in datatable matches what is really happening on login and access etc
|
||||||
|
|
||||||
-1 Schedule settings always on first setting shows nothing set for the color source even though it's defaulted to a known value?!
|
-1 Schedule settings always on first setting shows nothing set for the color source even though it's defaulted to a known value?!
|
||||||
|
-1 Schedule, what is the maximum number of techs can show in team view, can show more with scroll?
|
||||||
|
seeder should prevent going over this max (tags/prefilter/gen less)
|
||||||
|
|
||||||
-1 logged in as tech user tried to change status got not authorized when it was closed status?
|
-1 logged in as tech user tried to change status got not authorized when it was closed status?
|
||||||
yeah, tech user can't seem to set any locking status or maybe any status, they have "service techncian" only role
|
yeah, tech user can't seem to set any locking status or maybe any status, they have "service techncian" only role
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user