How does ISPConfig handle 1200 websites?

[hakong]

I will most likely be deploying ISPConfig and migrating some 1200 websites to it.
Anyone here deployed more than 1200 websites in ISPConfig, and if so, how does it handle it? Does it scale to that size?
Any tips and info appreciated, thanks!

[till]

The only limitation is your server hardware, not ispconfig.

[hakong]

Originally Posted by till

The only limitation is your server hardware, not ispconfig.

Ok, let me rephrase the question.

I wasn't talking about physical limits, like memory, disk space, or CPU power.
I'm talking about how ISPConfig handles so many entries, for example compared to other panels like cPanel, or Virtualmin.
They all handle things differently, some scale well up into the tens of thousands, others don't scale so well, regardless of hardware power.
With that said, your answer is to me like answering why the code

for website in ListOfWebsites
do
	for website in ListOfWebsites
	do
		for website in ListOfWebsites
		do
			CalculatePiToHundredDigits
		done
	done
done

doesn't scale up to a million websites if the intended function is to calculate pi to a hundred digits for every website with the answer "the hardware is the limit", in which case you'd better be off with better code

Also, what is the biggest number of websites you know of deployed on ISPConfig successfully without major problems?

[till]

Ok, if you dont take hardwareresources in account then ispconfig can handle currently about 4 million sites on a single install. ISPConfig handles each config change as single action, so the number of sites does not matter as long as the numerical ID of the sites fit into a int (unsigned) value field.

Also, what is the biggest number of websites you know of deployed on ISPConfig successfully without major problems?

Some users reported that they run a few thousand sites on ispconfig setups, but I dont have a exact number. In the last 5 years since ispconfig 3 exists we had not a single reported scaling issue that was not related to the hardware (e.g. ram).

[hakong]

Originally Posted by till

Ok, if you dont take hardwareresources in account then ispconfig can handle currently about 4 million sites on a single install. ISPConfig handles each config change as single action, so the number of sites does not matter as long as the numerical ID of the sites fit into a int (unsigned) value field.



Some users reported that they run a few thousand sites on ispconfig setups, but I dont have a exact number. In the last 5 years since ispconfig 3 exists we had not a single reported scaling issue that was not related to the hardware (e.g. ram).

Thanks for the answer!

[tom123]

Originally Posted by till

Ok, if you dont take hardwareresources in account then ispconfig can handle currently about 4 million sites on a single install. ISPConfig handles each config change as single action, so the number of sites does not matter as long as the numerical ID of the sites fit into a int (unsigned) value field.

Why not use a bigint ?

[till]

Off course we could do that when someone reports that he really runs more then 4 million sites on a single install, but I havent heard of a installation that hits this limit yet.