Conversation:

Notices

1. maiyannah (maiyannah)'s status on Sunday, 13-Nov-2016 21:27:39 EST maiyannah

   Remote profile options...

   • 馬鹿野狐(ばかやこ)✔
   @takeshitakenji MySQL is probably the bottleneck, I think.  4 MS/s isn't much disk throughput for a mechanical let alone (I'd think) a SSD.   What's your innodb_buffer_pool_size?  It's usually the first candidate for optimization.  Ideally you want it to be between 60-80% of available RAM depending on what else you're running on the system. You might want to c…
   • maiyannah (maiyannah)'s status on Sunday, 13-Nov-2016 20:47:25 EST maiyannah

     Remote profile options...

     • 馬鹿野狐(ばかやこ)✔
     @takeshitakenji Assuming you're on the daemons still, you can go to /scripts/ and spam php ./queuedaemon.php
   • maiyannah (maiyannah)'s status on Sunday, 13-Nov-2016 21:09:10 EST maiyannah

     Remote profile options...

     • 馬鹿野狐(ばかやこ)✔
     @takeshitakenji This instance's db and public_html are on a 5.2k rpm mechanical drive so I find it hard to believe you're hitting an I/O barrier unless the shares on your VM are astonishingly low.
   • maiyannah (maiyannah)'s status on Sunday, 13-Nov-2016 21:30:05 EST maiyannah

     Remote profile options...

     • 馬鹿野狐(ばかやこ)✔
     @takeshitakenji If you're only using MySQL locally, setting skip_name_resolve is a cheap and harmless performance gain.