ayanova/devdocs/todo.txt

@@ -24,13 +24,25 @@ AUTOMATED TESTING
 			Cypress will test e2e, can jmeter as well??
 
 
-todo: simultaneous users limit on droplet with reporting thrown in?
+
 
 
 todo: take a sample report and strip it to see where and what can be changed to speed up generation
 	there are lots of indications online when using puppeteer to gen docs that too many elements slow it down and some particular ones are killer for this
 
 
+todo: reporting failing on linux under load
+	well, not failing exactly, but eating up all resources and bringing to a halt
+	possible reporting issues solution: don't start a new report until last one finished
+	i.e. it should wait until the last report has resolved before spinning up a new one
+	this would resolve the linux issue I think where it gets overloaded because it's trying to do too many at once
+	maybe a setting for a hard limit on number of reports currently running or instances of chrome started by report
+	zombie processes?
+		https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
+
+	store process id in ram, have a job that periodically goes thorugh the list and looks for that process and kills it if more than 30 seconds old??
+		can store in ram because it's ephemeral and closing server would kill those processes anyway
+
 
 
 
@@ -417,6 +429,9 @@ todo: 3 Schedule form reporting?
  |_____/|______|_|  \_\  \/   |______|_|  \_\
                                              
                                              
+todo: 1`don't log user logins in INFO level, move down to debug or trace
+	however, *do* maybe insert it into the event log as a special event, I think there is a case here or in rockfish for that
+	it fills the server log with useless info
 
 todo: 1 Test with expired key, can superuser login and no one else?? **CRITICAL**
 todo: 1 erase database is way too fucking slow
@@ -437,7 +452,10 @@ todo: 2 make priority / woitem / wostatus colors distinct from each other
 	change from strong primary colors to more faded pastel colors
 	maybe priority in primary and status of both kinds more muted but also in different ranges so no clash
 		i.e. no two the same color or even close between each so in theory you can see at a glance which is which
-
+todo: 2 Server metrics don't seem to tell the story of teh overall server
+	i.e. when reporting is jammed up on linux and the server manager in do shows 100% cpu, inside the ayanova server ops metrics shows a much smaller number and responds
+	so it seems it's reporting only on ayanova's share of what is happening but if the overall server is bottlenecking we need to show that as well
+	
 todo: 2 make sample data appointments suitable for evaluation of calendar
 	spread throughout the day
 		right now a bunch are extremely close if not on the same time window for same wo