From c3798de19de3f90eda03158f38e14a7b87948c92 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sat, 1 Feb 2020 00:16:40 +0000 Subject: [PATCH] --- devdocs/todo.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 062ad261..96bf2756 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -10,9 +10,12 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ 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 + - 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 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