From bf5c6e1c805a0fe85c625d49d77179ab3c62787e Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 21 Sep 2020 21:56:42 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index dea17dde..762f1479 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -16,8 +16,19 @@ Ok, fixed it, but now it's a little slower and can crash if it hits the limits o Not sure what to do about that, maybe more timeouts in more places? What are the specs for the droplet? +todo: figure out how jsreport is launching headless chrome, i.e. which settings and flags etc +todo: look over this: https://github.com/puppeteer/puppeteer/issues/1834 +todo: look at guidance for running puppeteer (js) on alpine docker here: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-on-alpine todo: test with generated huge data locally here in Windows, see what limits get hit and how it handles it +todo: more timeouts for report rendering, Devops droplet is overwhelmed by 10k records of widgets using the customfields example report + symptom is super high cpu usage (100%) pegged and probably virtual memory usage as well + timeout is kind of a hard core way to work around this issue, maybe instead it should be looking at excessive cpu and memory usage? + The metrics don't catch it because it happens too quickly for the metrics lifecycle + + I want it to be able to handle it gracefully without crashing + +todo: look at metrics snapshot lifecycle, perhaps it should be shorter as it's missing 100% cpu pegging during big rendering on devops todo: pdf page numbers control look at jsreport what do they include in their pdf post processing parameters and capabilities @@ -27,6 +38,8 @@ todo: reporting load test test locally with 20k widgets, make it crash then determine what limits to set on it and properly return error when it's exceeded right now it just says something about puppeteer and "crash" +todo: Need a setting that warns people about printing too much data, i.e. "That's a lot of data, are you sure you want to render that, it will be slow" or something to that effect + todo: Take a serious look at .net5 migration, it will almost certainly be better to do it now than down the road after a release it also has many performance enhancements and nifty features like code analysis and warnings which might save me a lot of hassle @@ -39,6 +52,9 @@ todo: look at what's coming on the radar before release in the big libs I'm usin todo: triage this stuff: +todo: DataListFilter UI pretty shitty + error on duplicate + how to make a new filter?