Guest User

Untitled

a guest
Jun 22nd, 2018
72
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.51 KB | None | 0 0
  1. I've been looking into this a little and have a few comments so far. I noticed that you're serving the images from MySQL Resources table through Tomcat before being handed out through the nginx proxy.
  2.  
  3. I would strongly look at how you can change that, my first thought would be to serve static content such as images, css, js directly from the nginx instance, skipping the proxy for that. An alternative method would be to keep the static content within the DB as it is now, but populate a memcached server at the same time and use the nginx memcache functions to check for the content there before hitting Tomcat and
  4.  
  5. You mentioned in the previous ticket that you have Apache listening locally on port 80, the config of nginx though is set to bind to 80 on all IP's, Apache isn't running at all nor is there any config within it to proxy like that.
  6.  
  7. The biggest CPU use on the server is constantly coming from Tomcat which almost always has at least 2 CPU cores at 100% usage. The dotcms instance being the heaviest in load normally.
  8.  
  9. I would say that its essential at the moment to move static content out of the dynamic part, to clean up the delivery and decrease the load on your java so that it is not handling so many images.
  10.  
  11. I'll keep looking and see if I can come up with anything more concrete, the indications that java is suffering though means that theres likely not a lot that we can do with this, we don't have much experience with Tomcat, though I'm quite familar with nginx so will be looking at that side of the solution.
Add Comment
Please, Sign In to add comment