Hi Felipe,

Thanks for the quick response. I've eliminated it's cpu load on the 
production server by directing running the query on the mysql and 
calculation time is very quick. It's unlikely network issue because the 
ping is pretty quick.

mysql query time on the server:
1063 rows in set (0.00 sec)


ping 172.16.100.131
64 bytes from 172.16.100.131: icmp_seq=2 ttl=62 time=0.316 ms


On Tuesday, July 18, 2017 at 11:10:40 AM UTC-7, Felipe wrote:
>
> You need to see de CPU load in server.
>
> In your test you probably are using a local machine with no loading... but 
> your produce server I dont know. You need to see in server the webserver 
> too, try to run django-admin runserver <ip>:8000 and see if you have the 
> same issue.
>
> But if you are just connecting to another machine with database, and 
> application is in yur development enviroment, probably is your network.
>
> 2017-07-18 15:00 GMT-03:00 Kevin Yu <sams...@gmail.com <javascript:>>:
>
>> Hi All,
>>
>> I'm rewritting an web application using Django 1.11. When i hooked up to 
>> my test mysql database (version 5.7), the performance is amazing. The page 
>> renders within 1 second. However, when I connect to the existing production 
>> mysql (version 5.1), the page takes more than 10 seconds. 
>>
>> I installed the debug toolbar, and I found out the the query time is 
>> actually not the issue. Most of the time are in the CPU. 
>>
>> I am wondering whether the Django is having issues with older mysql 
>> version when Django receives the data and try to map it to objects via ORM.
>>
>>
>> <https://lh3.googleusercontent.com/-lti9EnCOwpI/WW5My639ZTI/AAAAAAAADes/gUJgzX0Wy5IvrGpf2xGDKFbAkoqN7za2gCLcBGAs/s1600/Screenshot%2Bfrom%2B2017-07-18%2B10-59-30.png>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com <javascript:>.
>> To post to this group, send email to django...@googlegroups.com 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/21e35905-047c-4d57-9f0c-6012d148597c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/21e35905-047c-4d57-9f0c-6012d148597c%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4280217c-b3e1-459b-9487-76a2776c323f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to