<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Elgg scalability</title>
	<atom:link href="http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/</link>
	<description>Making the world a better place, one byte at a time...</description>
	<lastBuildDate>Fri, 27 Jan 2012 17:12:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Morpheus</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-47470</link>
		<dc:creator>Morpheus</dc:creator>
		<pubDate>Sat, 17 Sep 2011 00:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-47470</guid>
		<description>I&#039;m trying to decide which platform to use for a new social network. It worries me that there&#039;s no clear answer here about scaling elgg onto multiple servers and how that can be achieved. If you are lucky enough to hit multiple millions of users, you need to be confident that a platform CAN scale. Not a case of cross that bridge IF it happens. I wouldn&#039;t buy a 1.1 litre car engine hoping it&#039;ll pull a big caravan. The easiest way to scale one server is to use server that will take lots of memory, multiple (multi core) processors, caching disk controller, sas drives, optimise the caching etc. At some point though this may not be enough. Ok use some front end caching proxy to take some load. But still you may need to scale to a multi server envronment. So that&#039;s the key point of my question and maybe many other peoples. Can you scale Elgg onto multiple backend elgg servers / sql databases, is there a method or guide for this, does elgg cater for this out the box? etc...</description>
		<content:encoded><![CDATA[<p>I&#8217;m trying to decide which platform to use for a new social network. It worries me that there&#8217;s no clear answer here about scaling elgg onto multiple servers and how that can be achieved. If you are lucky enough to hit multiple millions of users, you need to be confident that a platform CAN scale. Not a case of cross that bridge IF it happens. I wouldn&#8217;t buy a 1.1 litre car engine hoping it&#8217;ll pull a big caravan. The easiest way to scale one server is to use server that will take lots of memory, multiple (multi core) processors, caching disk controller, sas drives, optimise the caching etc. At some point though this may not be enough. Ok use some front end caching proxy to take some load. But still you may need to scale to a multi server envronment. So that&#8217;s the key point of my question and maybe many other peoples. Can you scale Elgg onto multiple backend elgg servers / sql databases, is there a method or guide for this, does elgg cater for this out the box? etc&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Povey</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-39778</link>
		<dc:creator>Marcus Povey</dc:creator>
		<pubDate>Wed, 13 Jul 2011 11:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-39778</guid>
		<description>The core should be &quot;relatively&quot; straight forward... you will need to create a compatible schema then modify the core get_* functions etc as well as the database initialisation code.

The real problems comes with third party plugins which have their own database queries ... we strongly recommended people didn&#039;t do this, but there is nothing we can do to stop them, and I know that many did.</description>
		<content:encoded><![CDATA[<p>The core should be &#8220;relatively&#8221; straight forward&#8230; you will need to create a compatible schema then modify the core get_* functions etc as well as the database initialisation code.</p>
<p>The real problems comes with third party plugins which have their own database queries &#8230; we strongly recommended people didn&#8217;t do this, but there is nothing we can do to stop them, and I know that many did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fadi</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-39684</link>
		<dc:creator>Fadi</dc:creator>
		<pubDate>Tue, 12 Jul 2011 11:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-39684</guid>
		<description>Hi,

I was wondering if I can connect elgg to another type of DB maybe oracle or even a nosql DB, how can I achieve this? even if it needs heavy customization. I would really appreciate is if you give me a head start.

also do u think it is better to do it on 1.7 or on 1.8?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I was wondering if I can connect elgg to another type of DB maybe oracle or even a nosql DB, how can I achieve this? even if it needs heavy customization. I would really appreciate is if you give me a head start.</p>
<p>also do u think it is better to do it on 1.7 or on 1.8?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Povey</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-29267</link>
		<dc:creator>Marcus Povey</dc:creator>
		<pubDate>Fri, 22 Apr 2011 08:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-29267</guid>
		<description>Never used them, so have no opinions one way or the other. :) 

Would be interested in hearing people&#039;s experiences though.</description>
		<content:encoded><![CDATA[<p>Never used them, so have no opinions one way or the other. <img src='http://www.marcus-povey.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Would be interested in hearing people&#8217;s experiences though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan de Dios López-Rienda</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-29199</link>
		<dc:creator>Juan de Dios López-Rienda</dc:creator>
		<pubDate>Thu, 21 Apr 2011 17:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-29199</guid>
		<description>What is your opinion about the following hosting option?

http://www.tmdhosting.com/elgg-cloud-hosting.html</description>
		<content:encoded><![CDATA[<p>What is your opinion about the following hosting option?</p>
<p><a href="http://www.tmdhosting.com/elgg-cloud-hosting.html" rel="nofollow">http://www.tmdhosting.com/elgg-cloud-hosting.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vivek</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-5290</link>
		<dc:creator>vivek</dc:creator>
		<pubDate>Sat, 19 Sep 2009 09:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-5290</guid>
		<description>A lot of you have been talking about having &quot;resonable&quot; hardware.  Is that defined for elgg?  For example what is the elgg community site hardware specs?  Is that common knowledge?  It would really help if some of you folks explain your real world hosting / clustering setups.</description>
		<content:encoded><![CDATA[<p>A lot of you have been talking about having &#8220;resonable&#8221; hardware.  Is that defined for elgg?  For example what is the elgg community site hardware specs?  Is that common knowledge?  It would really help if some of you folks explain your real world hosting / clustering setups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Povey</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-5062</link>
		<dc:creator>Marcus Povey</dc:creator>
		<pubDate>Wed, 09 Sep 2009 13:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-5062</guid>
		<description>Exponentials are always scary, but so far all growth on elgg systems appear to be fairly linear. 

Pre 1.5 there was an issue with scaling where plugins and views were concerned however this has been fixed - this may be what a couple of people have had concerns with in the past.

By way of example - Community.elgg.org is an active site with quite a few users. This site is running on vanilla elgg on a very modest server without any special tweaks. It isn&#039;t even running memcache as it ran fast enough without it.

With memcache enabled hits on the database drop dramatically as well, leaving most of the work done by the apache process.

My advice is still to walk before you can run. Get a good site going and then scale up. All scalability problems are solvable ones, and if it is necessary to perform modifications to the code then these can be accomplished when it is economical to do so (cost of development &lt; new hardware for equiv performance gain).

As you scale the database grows in size of course, so one could look at splitting reads and writes (support already built in). There are also sharding techniques to try but this would require some schema modification.</description>
		<content:encoded><![CDATA[<p>Exponentials are always scary, but so far all growth on elgg systems appear to be fairly linear. </p>
<p>Pre 1.5 there was an issue with scaling where plugins and views were concerned however this has been fixed &#8211; this may be what a couple of people have had concerns with in the past.</p>
<p>By way of example &#8211; Community.elgg.org is an active site with quite a few users. This site is running on vanilla elgg on a very modest server without any special tweaks. It isn&#8217;t even running memcache as it ran fast enough without it.</p>
<p>With memcache enabled hits on the database drop dramatically as well, leaving most of the work done by the apache process.</p>
<p>My advice is still to walk before you can run. Get a good site going and then scale up. All scalability problems are solvable ones, and if it is necessary to perform modifications to the code then these can be accomplished when it is economical to do so (cost of development &lt; new hardware for equiv performance gain).</p>
<p>As you scale the database grows in size of course, so one could look at splitting reads and writes (support already built in). There are also sharding techniques to try but this would require some schema modification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hakanolin</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-4822</link>
		<dc:creator>hakanolin</dc:creator>
		<pubDate>Sat, 29 Aug 2009 19:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-4822</guid>
		<description>A bit strange that you are not able to answer the question about scalability. 

Comments like the one above by C Marcel scares me: &quot;Whether my understanding of Elgg’s architecture is correct or not, the point is that a system’s performance can degrade exponentially as certain quantities grow. In such scenarios, no matter how much hardware you throw at that problem, you won’t fix it&quot;. 

Exponents always rules and ... exponents always scares. 

I was thinking yesterday: OK, I don&#039;t know much about this, but it looks nice. Lets go for it.

But, if Elgg does not not scale? Do you have any model of the scaling (even the simplest would do)? What is your idea behind scaling? 

To be more specific, how many servers (dedicated) are needed per user (or per 5% user mentioned above)? And how does it scale? Exponential use? A benchmark is not needed to make such an estimate.

(And, the site we are designing will have millions of users in the next few years (it is OK if you laugh). 2010 it will be 20 000. And, of course I worry, even if the failure probability for the site is large.)

Best regards,
Hakan Olin

PS And I think your Elgg is fantastic. Really ...</description>
		<content:encoded><![CDATA[<p>A bit strange that you are not able to answer the question about scalability. </p>
<p>Comments like the one above by C Marcel scares me: &#8220;Whether my understanding of Elgg’s architecture is correct or not, the point is that a system’s performance can degrade exponentially as certain quantities grow. In such scenarios, no matter how much hardware you throw at that problem, you won’t fix it&#8221;. </p>
<p>Exponents always rules and &#8230; exponents always scares. </p>
<p>I was thinking yesterday: OK, I don&#8217;t know much about this, but it looks nice. Lets go for it.</p>
<p>But, if Elgg does not not scale? Do you have any model of the scaling (even the simplest would do)? What is your idea behind scaling? </p>
<p>To be more specific, how many servers (dedicated) are needed per user (or per 5% user mentioned above)? And how does it scale? Exponential use? A benchmark is not needed to make such an estimate.</p>
<p>(And, the site we are designing will have millions of users in the next few years (it is OK if you laugh). 2010 it will be 20 000. And, of course I worry, even if the failure probability for the site is large.)</p>
<p>Best regards,<br />
Hakan Olin</p>
<p>PS And I think your Elgg is fantastic. Really &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Povey</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-4749</link>
		<dc:creator>Marcus Povey</dc:creator>
		<pubDate>Wed, 26 Aug 2009 11:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-4749</guid>
		<description>@pasta Largely that is a &quot;how long is a piece of string&quot; question :)

You are right that no benchmarks have really been done (and I would be interested in hearing your experiences), but to start you off:

Research done by Stan from Brighton Uni indicates that on a typical to high usage site you can expect to have ~5% of users active at any one time (this is typical usage, obviously you&#039;ll get spikes which you should probably be able to handle).

Memory wise during an individual page impression elgg generates some caching and temporary variables - so you can guess at about memory = site object + site query + user object + user query + dataset of page. 

CPU wise, all indications that we have done through profiling is that script execution is a negligible portion of the overall page load - on the order of ~0.02 sec depending on machine. 

In terms of hardware, our larger installs are still fairly modest in hardware terms (which is a good thing!), and if you were going to splash out on anything I&#039;d splash out on memory (which gives you memcache options).</description>
		<content:encoded><![CDATA[<p>@pasta Largely that is a &#8220;how long is a piece of string&#8221; question <img src='http://www.marcus-povey.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>You are right that no benchmarks have really been done (and I would be interested in hearing your experiences), but to start you off:</p>
<p>Research done by Stan from Brighton Uni indicates that on a typical to high usage site you can expect to have ~5% of users active at any one time (this is typical usage, obviously you&#8217;ll get spikes which you should probably be able to handle).</p>
<p>Memory wise during an individual page impression elgg generates some caching and temporary variables &#8211; so you can guess at about memory = site object + site query + user object + user query + dataset of page. </p>
<p>CPU wise, all indications that we have done through profiling is that script execution is a negligible portion of the overall page load &#8211; on the order of ~0.02 sec depending on machine. </p>
<p>In terms of hardware, our larger installs are still fairly modest in hardware terms (which is a good thing!), and if you were going to splash out on anything I&#8217;d splash out on memory (which gives you memcache options).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pasta</title>
		<link>http://www.marcus-povey.co.uk/2009/01/04/elgg-scalability/comment-page-1/#comment-4691</link>
		<dc:creator>Pasta</dc:creator>
		<pubDate>Sun, 23 Aug 2009 17:17:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.marcus-povey.co.uk/?p=124#comment-4691</guid>
		<description>Hi Marcus,

I have to install Elgg on a site with 50k users and we expect to have 500k in 2 years time. We need to provide an estimation in the amount of hardware required. I know that there are not real benchmark done and it all depends on the use etc... but do you know how much memory is each logged user consuming ? how many pages can elgg serve per second per CPU etc.... any data would be very usefull. I&#039;ve seen that elgg website has nearly 20k users. What kind of hardware are you using to serve it ? how many servers Apache, MySql in cluster etc ....

thanks !</description>
		<content:encoded><![CDATA[<p>Hi Marcus,</p>
<p>I have to install Elgg on a site with 50k users and we expect to have 500k in 2 years time. We need to provide an estimation in the amount of hardware required. I know that there are not real benchmark done and it all depends on the use etc&#8230; but do you know how much memory is each logged user consuming ? how many pages can elgg serve per second per CPU etc&#8230;. any data would be very usefull. I&#8217;ve seen that elgg website has nearly 20k users. What kind of hardware are you using to serve it ? how many servers Apache, MySql in cluster etc &#8230;.</p>
<p>thanks !</p>
]]></content:encoded>
	</item>
</channel>
</rss>

