Kane, splitting to three servers as you mentioned should give you some performance boost. You can also have separate server for files. After that, you would have to use cloud architecture for database servers, or partition your data.
Thanks guys. We're thinking that we should spend time analyzing the slow queries, maybe tweak some MySQL settings, before moving hosts.
Our server specs are pretty insane (quad-core Xeon processor, 8 GB RAM) for the size of our site, and our average memory and CPU loads are very, very low. So obviously something else is going on and the hardware isn't to blame.
@Dhrup, the reason the cron takes so long is it's sending and receiving data from 20 or so other sites via APIs and whatnot, so that wait time is really the bottleneck.
Cheers!
cron - ;) i see..
enabled slow queries log ?
disable elgg log.
cut down php error reporting
cut down apache logging
Yes that works I woke up to only a few spams this morning which was much easier to delete so thank you @Team Webgalli
I know it isn't a long term solution or even perfect, but it is a handy and quite lethal weapon to have at my disposal when need be, so thanks again.
I think an idea is to make a permenent cookie(which should be deleted while at the time of formatting the system),
while people visiting the website
if in cookie there is an already logged session of the site
{
, hide the registration page through server side scripting.
}
else (there is no logged session)
{
show the registration page
}
But all these ideas are neither 100% reliable nor 100% percent consistent. To forbid the registration through ip or any other process, it is only applicable at the time when all people are using unique computers by their own..
Any updates to this for 1.9? I would definitely be interested in this spam limiting since none of the plugins I've found have this option in them.
Yes that works I woke up to only a few spams this morning which was much easier to delete so thank you @Team Webgalli
I know it isn't a long term solution or even perfect, but it is a handy and quite lethal weapon to have at my disposal when need be, so thanks again.
I think an idea is to make a permenent cookie(which should be deleted while at the time of formatting the system),
while people visiting the website
if in cookie there is an already logged session of the site
{
, hide the registration page through server side scripting.
}
else (there is no logged session)
{
show the registration page
}
But all these ideas are neither 100% reliable nor 100% percent consistent. To forbid the registration through ip or any other process, it is only applicable at the time when all people are using unique computers by their own..
Any updates to this for 1.9? I would definitely be interested in this spam limiting since none of the plugins I've found have this option in them.
Yes that works I woke up to only a few spams this morning which was much easier to delete so thank you @Team Webgalli
I know it isn't a long term solution or even perfect, but it is a handy and quite lethal weapon to have at my disposal when need be, so thanks again.
I think an idea is to make a permenent cookie(which should be deleted while at the time of formatting the system),
while people visiting the website
if in cookie there is an already logged session of the site
{
, hide the registration page through server side scripting.
}
else (there is no logged session)
{
show the registration page
}
But all these ideas are neither 100% reliable nor 100% percent consistent. To forbid the registration through ip or any other process, it is only applicable at the time when all people are using unique computers by their own..
Any updates to this for 1.9? I would definitely be interested in this spam limiting since none of the plugins I've found have this option in them.
Yes that works I woke up to only a few spams this morning which was much easier to delete so thank you @Team Webgalli
I know it isn't a long term solution or even perfect, but it is a handy and quite lethal weapon to have at my disposal when need be, so thanks again.
I think an idea is to make a permenent cookie(which should be deleted while at the time of formatting the system),
while people visiting the website
if in cookie there is an already logged session of the site
{
, hide the registration page through server side scripting.
}
else (there is no logged session)
{
show the registration page
}
But all these ideas are neither 100% reliable nor 100% percent consistent. To forbid the registration through ip or any other process, it is only applicable at the time when all people are using unique computers by their own..
Any updates to this for 1.9? I would definitely be interested in this spam limiting since none of the plugins I've found have this option in them.
merci - à tous mes amis... ;-)
After all your suggestions and some messages, etc.
my tweaked code works OK now.. everything looks smooother now..
As I said.. "I aint *that smart... cwapssss ;-)..."
So I listened to all... esp Carlos's messages and your Skype ;-)
Helped to clear up the cobwebs in my head...
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.