Important CPU abuse from Php

Thanks for the tips guys!

The only SEF I run is the built in one in Joomla. Is this ok to use or does it create the same problem?

I have noticed a boost in performance after removing joomsef and using the built in one. Though I also enabled caching in the same time period so...

G'day irradiate. I use Webcity. One of the best decision I ever made in my entire life! Rock-solid, beautiful service! Ridgey-didge.

Give me a telephone call and we'll discuss what's going on (contact me by PM).

The core joomla sef thingie doesn't have any problem irradiate

G'day, irradiate. Thanks for your phone call late yesterday arvo. I'm sorry we didn't get to the root cause of your problem but I've had a think overnight and I wonder whether these theories might help.

To summarise the situation, irradiate has a working website that is based on Joomla 1.0.x with Simple Machines Forum and a bridge. He's looking for forum component that seamlessly integrates with Joomla (like all of us) and has decided to use Kunena. He wants to convert his SMF data into Kunena (involving over 46,000 messages and 1,500 message categories) and transport the forum data and his users to a new J! 1.5 website. The old J! 1.0 website runs off-shore; he's established his new J! 1.5 site here in Australia. His Australian hosting company claims that, for a period of time, the use of his forum was placing excessive processing demand on the servers and have threatened to cut-off his access if he doesn't do something about it.

We don't know the extent of the hammering that's directly due to Kunena. What's quite inexplicable is that the new J! 1.5 site is not yet in production. This means that the only server activity has been due to a handful of users.

I wonder whether the hammering of the webhost's servers occurred during the conversion from SMF to Kunena? I wonder whether was phpMyAdmin was instrumental ... not Kunena itself?

irradiate doesn't use any SEO components (which might have some impact on the number of SQL queries). As Matias has stated, it's not necessarily the volume of SQL queries, it's the way Kunena's queries are constructed that could affect processing performance.

I'm therefore as perplexed as irradiate is as to what narked his webhosting company (the same service that I also use and have no problems with) when he makes use of his website. If he allows users to his site, will it cause an unacceptable demand on server processor availability? Or perhaps the reported surge only occurred during the SMF-Kunena transitional phase?

Does anyone possess SQL performance metric analysis tools that might assist irradiate to pinpoint the source of the problems?

Thanks

sozz

Ask the host to provide some documentation of this abuse. My advice would be to install and test locally and do the conversion. When done upload and install a Joomlapack archive of the completed conversion to the remote server.