and just like Grav and Drupal are only available on Pro (I’m not being anti Pro licencing but never understood why WP is ok for GPL but not other choices)
easy, if you mean the installer. Wordpress is extremely popular and is allowed so it will draw people into the Virtualmin Eco system. Joomla and other platforms are not that popular so would not make a good loss leader.
1 Like
WordPress brings in a lot of new users who convert to Pro, so many new users who convert to Pro that it pays for development of more WordPress related stuff like WP Workbench (which in turn helps pay for development of Virtualmin itself). Those others don’t, not even close. WordPress dominates the industry for small/medium business websites.
In short: WordPress is a loss leader with a decent conversion rate. The others just cost us time and money to maintain.
You should be enthusiastic about our support of WordPress, because it helps pay for the parts of Virtualmin you need/use.
2 Likes
I do keep a lot of backups on the disk, so maybe that might be contributing? But aside from that there’s nothing else on the server that consumes anywhere close to 100% of the cpu. What’s so CPU intensive in the collection script?
Unless I am misunderstanding something I’m guessing Stegan means that if people aren’t using WP Workbench then it should be excluded from the collection script? I do have a Wordpress blog on the server but I installed it the old fashioned way (i.e not via Virtualmin) so I do not need any WP Virtualmin features myself (so if WP Workbench is what’s causing or contributing to the high CPU spike then I think it would be a good idea for it not to run on this server).
Why would anyone assume WP Workbench would have any impact on systems without WordPress instances?
Did the wordpress installer script get removed when workbench was made?
No. This conversation is going crazy places. I have no idea what’s happening.
1 Like
Even with multiple WordPress instances installed, the impact is minimal. For example, I have 30 instances across different machines, with data collected through Webmin Servers Index module for some and locally for others. Even in that setup, the total collection time is about 40 seconds.
But if you have around 5–10 local WordPress sites, it only adds roughly 5 extra seconds overall. Perfectly reasonable and barely noticeable.
For anyone seeing collection.pl problem, there is a new webmin stats sub-command, which will only be available later in the upcoming Webmin 2.600. However, you can apply the patch manually now and use it to get more details about Webmin processes and memory usage.
It explained here:
1 Like
Because of @Ilia’s first comment in this thread:
I guessed him mentioning it was because it is known to cause high loads? (If that isn’t the case maybe @Ilia can clarify why he thought it was worth mentioning?)
Whatever the reason I think we just need to identify what is causing the high CPU usage and whether it can be switched off or extracted into a separate job or the whole collection script set to run every hour or few hours etc…
There’s really nothing to clarify here. In the first place, I just wanted to note that having WordPress websites with the WP Workbench plugin installed and active will naturally add a bit to the total collection time, which is completely expected. There’s nothing wrong with that. And, as mentioned earlier, you can always disable it in the module’s configuration if you prefer.
1 Like
“with many WordPress sites on the system”
Don’t have WordPress? You don’t have the overhead Ilia mentioned.
1 Like
If we have ruled out Wordpress (I have one blog on the server and do not use WP Workbench or any Virtualmin WP tools) what could be causing the high CPU usage?
Can anything be extracted into its own job and then run less frequently? Or maybe the collection script as it currently stands can be run less frequently without any concerning downside? (Think you said hourly is fine, does that still stand?)
Heh! I did not want to start another Wordpress war! you know and possibly everyone know I hate it with venom.
though I do understand why those who use it get driven down the same 
that keeps it alive. I just opt out of anything to do with it.
I only joined this topic because “WP Workbench” was mentioned as perhaps being involved - it was not me.