ayanova/devdocs/todo.txt

@@ -11,6 +11,24 @@ todo: look at proper settings for rendering in docker on linux and try to make i
 		check cpu, memory usage upon render request, reject immediately if the system is overburdened
 		check for running chromium processes or some way to determine if in the middle of the last render for someone
 
+		Try a method to zap all chromium processes as a test to see if they *can* be killed whil stuck this way
+		To test use the "custom date time format helpers" with 5k records, that reliably freezes everything even when others all seem to run ok
+			(this in itself is curious but whatever)
+
+	What I'm seeing is on a long render it returns a 504 gateway timeout to the client but it's still churning away in the background
+		5k records and "custom date time format helpers" report will take about 3 minutes to render, maybe less and it will crash out for the client return 504 but then it will complete at some point
+		Confirmed it *does* complete because I was able to download the 4.12mb 2144 page pdf manually from the server temp folder via filezilla once I saw the cpu go down again
+			and chrome process stop
+		90% memory is the max used in do graph panel, probably docker is not letting it take all or something isn't
+			maybe swapping out is what's happening, peak memory usage seems to be half a gig or so but c
+		97% cpu usage is max
+
+		I'm thinking it's a memory issue more than a cpu issue because the cpu is hardly pegged at all while it's rendering right up until it appears to run out of memory
+		then it starts swapping and all hell breaks loose and the cpu pegs on the swap daemon
+		Need to test by moving up to 2gb of memory witha  resize but keep the single vcpu and see what's what
+		also increase the timeout in nginx for the reverse proxy to wait 
+				
+
 
 todo: take a look at front end cypress testing etc again, it's going to be the best way to assure quality going forward and indespensible for smoke / load testing