From 430143dfbe34059af3cf8f973e3f932439a77069 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 21 Oct 2021 19:04:14 +0000 Subject: [PATCH] --- ayanova/devdocs/test protocol.txt | 30 ++++++++++ ayanova/devdocs/todo.txt | 91 +++++++++++++++---------------- 2 files changed, 74 insertions(+), 47 deletions(-) diff --git a/ayanova/devdocs/test protocol.txt b/ayanova/devdocs/test protocol.txt index aee28b9c..c35bfb86 100644 --- a/ayanova/devdocs/test protocol.txt +++ b/ayanova/devdocs/test protocol.txt @@ -128,3 +128,33 @@ Firefox browser MS EDGE browser + + + +SEEDING PERF LEVELS: + +//WINDOWS Installed PG server: (debug) +2021-10-20 14:42:17.8716|INFO|Seeder|Small level sample data seeded in 15 seconds +2021-10-20 14:45:17.1372|INFO|Seeder|MEDIUM level sample data seeded in 2 minutes and 2 seconds +2021-10-20 14:54:46.5645|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 19 seconds +2021-10-20 15:38:00.4839|INFO|Seeder|HUGE level sample data seeded in 38 minutes and 27 seconds +(weirdly it's slower in call cases but not by much) + +//WINDOWS with standalone pg (debug) +2021-10-20 15:42:38.9969|INFO|Seeder|Small level sample data seeded in 15 seconds +2021-10-20 15:45:21.3240|INFO|Seeder|MEDIUM level sample data seeded in 1 minute and 52 seconds +2021-10-20 15:56:08.5573|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 10 seconds +2021-10-20 16:32:24.6365|INFO|Seeder|HUGE level sample data seeded in 34 minutes and 5 seconds + +//WINDOWS with standalone pg (RELEASE MODE) +2021-10-21 08:36:45.3984|INFO|Seeder|Small level sample data seeded in 11 seconds +2021-10-21 07:35:08.3904|INFO|Seeder|MEDIUM level sample data seeded in 1 minute and 17 seconds +2021-10-21 06:25:48.8241|INFO|Seeder|LARGE level sample data seeded in 3 minutes and 18 seconds +2021-10-20 17:26:12.6142|INFO|Seeder|HUGE level sample data seeded in 28 minutes and 30 seconds + + +//LINUX SERVER comparison useful for relative perf calculations to have idea of variance (release, not debug) +2021-10-20 23:45:55.8145|INFO|Seeder|Small level sample data seeded in 11 seconds +2021-10-20 23:48:33.3221|INFO|Seeder|MEDIUM level sample data seeded in 1 minute and 15 seconds +2021-10-20 23:52:47.8938|INFO|Seeder|LARGE level sample data seeded in 2 minutes and 50 seconds +2021-10-21 00:19:23.8220|INFO|Seeder|HUGE level sample data seeded in 22 minutes and 48 seconds \ No newline at end of file diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 6d5a8664..cf9d9cfb 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -11,44 +11,40 @@ + +AUTOMATED TESTING + NEEDS: + Acceptance "smoke" testing to ensure can release confidently "E2E" testing + After code changes need compliance test that everything is still working + must be end to end so that all aspects are tested as much as possible + must be runnable here or against devops + Cypress will test e2e, can jmeter as well?? + + Load / capacity / stress testing + Find problem areas - dev / pre-release + Have an idea what hardware can support what load of users - marketing/ support / sales + how far can it go before failure? + what is the maxium simultaneous users for a given hardware config + digital ocean can help with this as we can spin up progressively more peformant droplets and load / stress test them to know + Does it recover from failure? + Find prior unknown bugs that result in failure under stress + + + Tools / links + https://www.digitalocean.com/community/tutorials/an-introduction-to-load-testing + jmeter + https://jmeter.apache.org/ + https://www.digitalocean.com/community/tutorial_series/load-testing-with-apache-jmeter + + TODO: + Find out if jmeter can be used for smoke and stress testing or do I still need to use cypress for smoke tests + how to install cypress standalone and remove vuetify outdated one? + + + Prioritize items to get to beta fast as possible 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: perf, test installed postgres vs standalone jimmied one vs DEVOPS server for same op - YES, very important to know this, is my cobbled together standalone postgres as good as installed or huge diff?? - - - -SEEDING PERF LEVELS: - - -//WINDOWS Installed PG server: -2021-10-20 14:42:17.8716|INFO|Seeder|Small level sample data seeded in 15 seconds -2021-10-20 14:45:17.1372|INFO|Seeder|MEDIUM level sample data seeded in 2 minutes and 2 seconds -2021-10-20 14:54:46.5645|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 19 seconds -2021-10-20 15:38:00.4839|INFO|Seeder|HUGE level sample data seeded in 38 minutes and 27 seconds -(weirdly it's slower in call cases but not by much) - -//WINDOWS with standalone pg -2021-10-20 15:42:38.9969|INFO|Seeder|Small level sample data seeded in 15 seconds -2021-10-20 15:45:21.3240|INFO|Seeder|MEDIUM level sample data seeded in 1 minute and 52 seconds -2021-10-20 15:56:08.5573|INFO|Seeder|LARGE level sample data seeded in 4 minutes and 10 seconds -2021-10-20 16:32:24.6365|INFO|Seeder|HUGE level sample data seeded in 34 minutes and 5 seconds - - -//LINUX SERVER comparison useful for relative perf calculations to have idea of variance - - - - - -------------------------------------- todo: two emails with change to reports to add and also cases regarding naming in light of removing unitmodel number field for consolidated name field some viz fields have old names / reports need updating @@ -61,31 +57,30 @@ todo: hard cap on appointments brought back controlled by client in settings oth todo: hard cap timeout on anything very time consuming like report generation, datalist queries, schedule etc if a report ties up the server for more than XX seconds it should stop it adn return an error too big - - - + can't have server churning when user abandons op + cancellable report job? + simultaneous users reporting?? + need stress / load testing setup to really get into this properly todo: should some things that were tagified be reverted back like in v7 due to reporting and other issues? -todo: firefox schedule fix: - https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925 - - - todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated - - TODO: 2021-10-15 15:03:10.9008|ERROR|AyaNova.Biz.TranslationBiz|********* GetSubsetAsync problem: Duplicate keys: UnitModelName - TRACK: + Reports, where it's at and about muted style for them style from dashboard design principle book where every non essential item is a distraction (table grids etc) also would prefer monchromatic with just a tinge of color if any - load and concurrency testing for confident release + + + + + + Customer work order form / view / open??? Customer CSR form has a bunch of todo in the template, WTF? Dashboard / widgets @@ -248,6 +243,8 @@ function ayGroupByTag(reportDataArray, tagContains) { \_____|______|_____|______|_| \_| |_| +- 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925 +- 1 todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated - 1 double check roles at client, the way authorizationroles.hasrole is coded makes me think it might be wrong it only checks that the value is nonzero but in postgres I noticed it needs to compare if the resulting value equals the exact role being checked