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

Browse Source
This commit is contained in:
John Cardinal
2020-02-01 00:16:40 +00:00
parent 1c5765e604
commit c3798de19d
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
devdocs/todo.txt
View File

@@ -10,9 +10,12 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ
TODO: HUGE BURN TEST OVER WEEKEND TODO: HUGE BURN TEST OVER WEEKEND
- Currently with huge dataset burn test takes 11 hours - 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 - 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? - so start it friday night with 4300 runs and observe over the weekend, does it get slower?, crash?
- Ideally need to do this with the server as well once next release is posted there - Ideally need to do this with the devops server as well once next release is posted there
TODO: HOw is it that I'm able to login and view widgets while the server is seeding?
- shouldn't it be locked out for any non-ops actions?
- There should be some kind of client UI that handles this like an overlay on screens where there is no access or a redirect to an no-access page or something
DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER