Open abrahamq opened 8 years ago
Maybe this has to do with the check-wifi script again? Or maybe it's connected to the bugs in the webserver?
I'm still a little dumbfounded on why this happens as well. Is it every time now? It always seemed to be random for me.
Looks like we may want to try ngnix (https://www.reddit.com/r/Python/comments/1t1sed/mod_wsgi_slow_to_respond_on_a_raspberry_pi/)
Hey, I'm hosed with final projects, but will be very free after Thursday afternoon to help however I can. We're also having some different trouble: we got a whole node built (with radio and configuration), but we're not seeing the data base update across the two nodes. We can see in the hamnet panel that the radios see each other, but we don't think that the databases are updating- not sure where in the stack we're going wrong.
Thanks!
On Mon, May 9, 2016 at 3:19 PM, Chad Spensky notifications@github.com wrote:
Looks like we may want to try ngnix ( https://www.reddit.com/r/Python/comments/1t1sed/mod_wsgi_slow_to_respond_on_a_raspberry_pi/ )
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/mit-ll/CATAN/issues/8#issuecomment-217961918
It's random, but happens more often than not- maybe like 70 percent of the time too slow to use.
Does it always happen during set conditions? Like is always slow right after start-up or after your first person entry?
On Mon, May 9, 2016 at 3:28 PM, Abe notifications@github.com wrote:
It's random, but happens more often than not- maybe like 70 percent of the time too slow to use.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/mit-ll/CATAN/issues/8#issuecomment-217964370
Nope, there's no pattern we can see. Sometimes it is slow, sometimes not. We're looking around to see if the check_wifi.sh script is interacting with this at all- maybe the script isn't actually working?
After connecting to the CATAN AP, the webpage is extremely slow to respond- requests take more than 2 minutes.