ovis

I'm having this prob. with the who's online and the visitators statistics modules, sometimes they just show to much, to many guests online, and the visitators statistics just goes up an up... by thousands.... anyone knows why? and what can i do to fix it?

thanx

worldnick

yeah i have this problem also, I suspect there is a query error, I am going to have to figure out how to monitor my queries and get more sophisticated.... no matter what I do mambo is running incredibly slow. My front page takes like 10 seconds to load etc..

fermambers

My front page also load slow and I'm using 4.5.2.2.

GRAM

It may not be fixable. The numbers shown in the whos online module are counts of the number of sessions currently in your session database table. If someone who visits your site has their browser security settings set very high (refuse cookies), mos will be unable to write their session cookie. This means on the very next page request they make, they look like a brand new visitor and mos creates a new session record for them. It then tries to write a cookie again to track the session.

Next page request will cause the same problem. You end up with a session record for every page they load.

You will notice this a lot when search engines drop by. They will not accept cookies, so they will end up adding a session for every page in your website that they index. There is a good chance when you notice unusual spikes in the numbers that you have just been spidered by a search engine.

The only thing you can really do about this is to set your session length relatively short in the site settings under administrator.

__________________
GRAM

Road Star Clinic / MLSHomeQuest.com

GRAM

It is probably not a Query error, as that would cause other problems. It takes a while to optimize a site for quick page loading.

First page loads, when a visitor hits your site for the first time, can take a moment as Mambo is setting up a session for them and writing a cookie to their browser (in addition to whatever else it would normally do for that page). Their browser is also downloading the CSS file and if set up to cache, caching the pages. Be sure to track the difference between first page load and subsequent page loads.

To check this you will need to clear your own cache(delete all temporary files in your browser), delete your cookies, and shut down your browser (to clear its memory cache). Restart your browser and load your page. Compare the time it takes for the first page to load, to the time it takes to return to the first page from any other page on your website (load it the same way both times, don't use the home menu option to hit the front page the second time if you used the domain name only the first time). If the urls in your browser are identical you should be able to get a fairly comparably set of page load times. It would be a good idea to repeat this process a couple of times to get a good average for each scenario, and reduce the potential for the server's utilization on a specific page load to mess up your time measurements.

If you are on a shared server, your server's utiliization can play a big part in this. Most ISPs who sell space on shared servers will put thousands of websites on a single server. On this one look for differences in page loads from different times of day. If it consistantly loads slowely during what would be peak usage times, you may be having a problem with server utilization. I have seen a new module on mamboforge.net that reports utilization, but have not tried to use it yet.

Other things that can affect page loading include your choice of editor (mine is set to none), the number of modules included in the positions displayed for your page, the number of spaces (and entries) in your css file (typically only effects first page load), the use of statistics tracking (set in Admin), and the number of external files (graphics - and how large they are) required to load your page.

__________________
GRAM

Road Star Clinic / MLSHomeQuest.com