Here is something odd. I was looking through the logs of nginx and uwsgi
to see if there are any smoking guns there. In the uwsgi log file I can at
least see the log contains the same time I experience in "real time" when I
select the page:
[pid: 2767|app: 0|req: 700/1896] 67.161.165.180 () {50 vars in 1007 bytes} [
Tue Jul 2 23:45:17 2013] GET /swim_smarter/results/meetevents/?meet=4232&
event=22F&pf=f => generated 6353 bytes in *3132 msecs* (HTTP/1.1 200) 5headers
in 218 bytes (1 switches on core 0)
So uwsgi sees the same time delay I see. I don't know if this is due to
uwsgi or which other component. I'm not very familiar with nginx and uwsgi
and may have misconfigured it when setting it up. It may be that a
different web server would be a better fit for my goals.
Eventually this will be a very heavily used database application with many
gigabytes of data, but it may take a year or two to build up to its full
potential. I could start with something simpler to configure and upgrade
it as the volume builds.
Joe
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
