I'm looking for web hosting companies or web hosting server administrators that are using the Webuzo control panel within a large production environment. Specifically in regards to how well it performs at scale.

We've been investigating utilizing Webuzo internally. I'm currently a bit stalled due to the lack of configuration templates for various services.

But upon investigating this, I found that Webuzo rebuilds it's entire Apache VirtualHost file - /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf - every time a modification is necessary. If a new account is added, the full /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf gets rewritten. An account gets deleted, the full /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf gets rewritten. An account adds an addon domain, the full /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf gets rewritten. I have concerns over how well this scales.

It's one thing when you have one, two or maybe up to 50 VirtualHosts. But what happens if you have 1000 or 2000 VirtualHosts on the server? That constant rewriting of the /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf file would seem to start a performance hit. Especially when you factor in other processes that might be consuming CPU time in a real production server.

As we're not yet using Webuzo in production environments, we can't really test this at this scale. I'm not sure if there are a lot of Webuzo control panel hosts out there, and where they exist in terms of this level of scale, but I thought I would ask. Any Webuzo hosts out there with a significant number of accounts and VirtualHosts are you seeing any performance issues related to this full /usr/local/apps/apache2/etc/conf.d/webuzoVH.conf rewrite?