Hi All,
Recently we have been experiencing periodic performance issues such as long page loads. This is only during peek hours of 140+ concurrent users and does not occur all the time. When issuing a top command on the server, I notice some httpd processes taking ~20% CPU. Is this normal for an Elgg instance? It could potentially be a plug-in causing this, I just wanted to reach out to the community and see if anyone else has experienced this.
Quick overview on our implementation:
Elgg 1.8.16
Web Server
Os: Linux/SUSE
CPUs: 4
Memory: 4Gb
Apache: MPM Prefork
Database Server
Same as web server
Could this perhaps be a hardware issue?
Thanks Elgg Community.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Cim@manacim
Cim - 0 likes
- Nikolai Shcherbin@rivervanrain
Nikolai Shcherbin - 0 likes
- Stan Drozdetski@StanD
Stan Drozdetski - 0 likes
- Matt Beckett@Beck24
Matt Beckett - 1 like
- Alex McFarlane@mcfarlane.am
Alex McFarlane - 0 likes
You must log in to post replies.What plugins are you using? Also why not use Nginx?
@Alex McFarlane Many reasons for this issue. More information about Elgg Performance & Scalability
Excellent list, RvR - I highly recommend one of the resources cited, https://elgg.org/discussion/view/310368/recommendations-for-a-medium-to-large-elgg-site. The MySQL section describes problems with table-level locking on a MyISAM engine, definitely something that we suffered from.
Switching to innodb has pretty large gains, separating the database from the file server, and offloading search to SOLR (or some other dedicated search app) is huge. Search is the slowest queries of anything contained in default Elgg, it's why I've spent so much time building the elgg_solr plugin, we use it in ~80% of our projects.
Thanks for the resources and the replies everyone, this will be a great starting point for us.