Are you running the database on the same host as your app?  Are you doing a
lot of joins or other complex data manipulation?  If both of these are yes,
you may want to consider switching to a more robust database platform.

On Tue, May 15, 2018, 1:41 PM Leonardo Mata <[email protected]> wrote:

> Hello there, I'm currently facing an issue on tuning my application o
> Amazon AWS EC2 instance.
>
> My currently configuration is a C5.xlarge instance with python 2.7 running
> on default amazon imaga. It uses apache httpd24-2.4.33-2.78 and
> mod24_wsgi-python27-3.5-1.25.amzn1.x86_64. This instance has 8GB Ram and 4
> vCPUs.
>
> My application is a Flask  with sqlalchemy to connect into a mysql db.
>
> I'm running a load-test with my own application with the most common
> routes weighted by usage. So it is most like a real usage of this
> application.
>
> The configuration for wsgi has 10 processes and 40 threads, but no matter
> how I change the configuration, the maximum req/s I can reach with a decent
> response time is around 80req/s. More than that causes cpu burn at 100%.
>
> Do you think it is possible to get better usage of CPU changing the number
> of process and threads or am I into a bottleneck of performance because of
> this cpu intensive behavior of my application?
>
> Thanks for the answer.
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/modwsgi.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to