I don't know if that's possible with elgg.
Is it possible to have two elgg sites, each one in a different server, using the same database installed in another server? Or is this something not possible til elgg 2.0?
Background story:
I'm using PiGo (based on elgg) on a intranet network, and it is currently installed in a Dual Intel Xeon 3.06 Ghz with 4 GB of RAM. I've been having issues when I have 50 users connected at the same time taking tests. So I was thinking to install elgg in two desktop computers and keep the database on the main server. I can't get a VPS because there's no internet service because it is a remote area.
Thanks!
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.
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- What the problem is?
- What resources the problem needs?
- Where those resources are needed?
- rjcalifornia@rjcalifornia
rjcalifornia - 0 likes
- What the problem is?
- What resources the problem needs?
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- iionly@iionly
iionly - 0 likes
- rjcalifornia@rjcalifornia
rjcalifornia - 0 likes
- Cim@manacim
Cim - 0 likes
- rjcalifornia@rjcalifornia
rjcalifornia - 0 likes
- Cim@manacim
Cim - 0 likes
You must log in to post replies.I don't understand what you are trying to achieve by two sites using the same database. Usually it is done the other way around: there is one site whose database has been installed on two different servers. That way there are two servers taking care of the database of a single site = the site becomes faster.
Have you done research/measuring so that you know:
You need to know the reason behind the performance issues before you try to fix it. There's no point in splitting the database if the slowness is caused by serving large images from the dataroot. And there is no point in caching images if the slowness is caused by a javascript that eats browser memory.
@Juho
Not enough RAM on the server (4 GB)
More RAM. The rest of the computers are at least 800 Mhz, can't be used as servers.
I already did tests with a clean install of elgg. Same issue. After the 50th user connect, elgg start sending "Fatal Error" pages.
What I want to do is: 25 users connect to one address and the other 25 users will connect to a another address, avoiding "Fatal Errors" due to many concurrent connections.
What processes are using the RAM? The connections to the web server or the connections to the database?
You could also try to optimize my.cnf to reduce the memory requirements of mysql. The default values (maybe not even set in my.cnf explicitely) could result in higher memory consumption per connection than necessary. By reducing size of buffers etc. it might not even be a slower performance but it could reduce the overal memory usage.
@Juho
Connections to the Web Server.
@iionly
I will try that tomorrow morning. I'm gonna run some stress tests and report back :D
@RJ check this out: https://community.elgg.org/discussion/view/2223983/web-server-clustering-for-elgg-based-sites
@Cim
Thanks! What Jerome says is exactly what I want to do. But I don't know how to do it.
Np RJ