But I can't believe that 30 MB is needed only for CB integration in that module... Thats more as the most hoster have as standart...

You're loading CBs entire library, that's an entire component, on top of your module. That is the total memory usage for the entire page load, almost all of it is cleared the instant the PHP has finalized, which none of it occurs at the exact same time.

And the memory is more the problem as the queries. So I can't publish the forum module on my startpage because the memory usage is to high and I get only a white page...

Then don't use the module or implement some caching to the module or active server side caching or enable Joomla caching. There's nothing I can do. You're loading 2 extensions on top of one another on top of the page being viewed and whatever else it's loading.

If you've that high traffic and high demand of a site you should review having your memory limits increased. We've no issues locally, Joomlapolis, or with any other users who have large userbases running into memory walls. CB has increased in efficiency substantially with recent releases and is only improving further with subsequent releases.

Kunena alone, according to your reports, is 24 MB. Why is CB receiving so much flak when it's more then double the size of Kunena code wise yet is only 30 MB. Both are EXTREMELY efficient for their sizes and functionality. Kunena has done an absolute wonderful job for efficiency to allow even us to use it here with a massive userbase where CB integration is also enabled.

It's very likely something configured on your host or in your install could be killing performance. I can't say specifically what however. You'd need an install which was only Joomla + CB + Kunena with your user base imported over to test true efficiency of just them factors involved.

Again, we're still looking into this though so that absolutely does not rule out a problem on our end. There's just nothing more I can do or advise at this time until we've a better understanding of why this is happening, large query count that is.

Do you have a php code cache/precompiler (e.g. APC) installed and configured ?

Hi Roland,

After discussion with Matias from Kunena team and investigation by them, your queries seem to be due to an incomplete upgrade of Kunena 1.6.

We could not reproduce them here, and those queries do not come from CB.

Best is to do a fresh install-over of latest Kunena 1.6.5, making sure all Kunena folders are writable for the upgrade, and try again. If issue persists, please check with Kunena team.