From 047448f9d1f015e670941ba5716a73ce5896931a Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 14 Sep 2022 12:58:10 +0000 Subject: [PATCH] --- devdocs/todo.txt | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index c69aa0df..fd844c03 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -11,8 +11,11 @@ Get stress test running, need to be sure 2022-09-13 17:26:59 60 users 86% cpupeak, 5.76 loadpeak, 3.85 endload, cpu 85%!, 78% mem peaked at end ** First Errors in the test output from jmeter, priors did not error out Peak errors (87%!) 4 minutes into test then drops off, caching? This is too many errors to be reliable. 2022-09-13 19:06:14 10 users 78% cpupeak, 1.39 loadpeak, .1 end load, cpu 15%, mem 58% 2022-09-13 19:26:33 50 users 75% cpupeak, 4.48 loadpeak but at end weirdly, peakmem 48% *Very minor errors 1.7%error was most then dropped, found at early peak load. All load ramped up smoothly over time unlike other runs that were opposite. also watching plex maybe affecting things - 2022-09-13 19:47:04 40 users (trying to find error range) + 2022-09-13 19:47:04 40 users 0 errors (trying to find error range) + 2022-09-13 21:30:07 40 users LONG LOAD 8 hours (28,800seconds) crash test see if it crashes or keeps chugging + no crash keeps chugging, super minimal errors looking like maybe when server rebooted spontaneously a few times which is weird, down for about 20 seconds each time + maybe the reboot is not the server booting but linux systemctl or dotnet restarting the service Stress test todo: Realism @@ -26,6 +29,14 @@ Stress test todo: Download or fake download report files, wait on report jobs? +SUBSCRIPTION CHANGES +ATTACHMENT / DATA CAP have a maximum attachment / data cap size that can be configured for subscriptions +STRIP OUT METRICS (maybe some of them for both types, just not working or accurate, the db and file size stuff is useful if working properly) +OPS - subscriptions don't need almost all of ops nor should they have it, is any info leaking that shouldn't go through it remove with a machete (tied to build type) +DOCS - ops section of docs not relevant to subscribers, add "PERPETUAL BUILD ONLY" maybe at top or something? +METRIC WE DO NEED + just a simple value showing storage space available for subscribers maybe usage over time? + but surface outside of OPS tree in menu, in admin? backup? reorganize below and then whatever is most urgent @@ -36,7 +47,6 @@ PRICING / COSTS Done! -- Update RAVEN and ROCKFISH license issuing, user count checking to solely go by active login users - Launch a trialing server, can start small and work up but keep all users on it so to save money and not any of our own corporate infrastructure servers "All free trial subscriptions are located in New York data center. Paid subscriptions can be in any of the following data centers of your choice ...blah blah blah."