This commit is contained in:
@@ -5,14 +5,10 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ
|
||||
|
||||
## IMMEDIATE ITEMS
|
||||
|
||||
|
||||
|
||||
TODO: Any code at the server that access the db or does file IO MUST be async top to bottom!!
|
||||
- FileUtil may have a bunch of IO stuff
|
||||
|
||||
TODO: REFACTOR GetNoLogAsync function is used in many places redundantly when the logging version could do the same thing but not log it with an optional bool switch so refactor that shit
|
||||
TODO: REFACTOR biz objects have two creates, an async and sync one, WTF is that about? See if can make it just one async version.
|
||||
- https://docs.microsoft.com/en-us/aspnet/core/performance/performance-best-practices?view=aspnetcore-3.1
|
||||
|
||||
TODO: REFACTOR BIZ objects have getbiz internal which can be removed and just check if httpcontext is null
|
||||
|
||||
TODO: Seeder create widget is creating a new widgetbiz each loop iteration but create user is not, try both ways and performance test
|
||||
|
||||
@@ -33,6 +29,15 @@ TODO: DataFilter how to distinguish between filtering on specific ID value or on
|
||||
- Might need to add a filter on ID type of thing maybe?
|
||||
- Wait and see...YAGNI scenario maybe
|
||||
|
||||
TODO: Need to test for memory leaks
|
||||
|
||||
TODO: HUGE BURN TEST OVER WEEKEND
|
||||
- Currently with huge dataset burn test takes 11 hours
|
||||
- If start Friday night can do 4.3 runs of 1000 and be done by Monday morning to analyze the results
|
||||
- so start it friday night with 4300 runs and observer over the weekend, does it get slower?, crash?
|
||||
- Ideally need to do this with the server as well once next release is posted there
|
||||
|
||||
|
||||
DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER
|
||||
|
||||
TODO: the license being logged breaks the format of the log file because it has line breaks etc, so instead, maybe log out as a single line (remove breaks)
|
||||
|
||||
Reference in New Issue
Block a user