without wassup the blog loads in less than 10 seconds - with it activated it can take up to a minute. I've tried unchecking the spam features in wassup to no avail. Any suggestiong? Using wordpress 2.7
thanks
wassup slows blog loading
(7 posts) (5 voices)-
Did you enable the Wassup Widget? It could slows down the blog if you get a lot of visits.
Posted 3 years ago # -
sph
MemberHi - I'm seeing the same. I have a small blog under development with just a handful of test users. Normally pages load in ~2 seconds. With the plugin enabled the loading tiem slows to maybe ~10 seconds. (These measures when runngin over my local LAN)
I don't have the widget enabled and have turned off all spam & referrer tracking (This will be a small private blog - I'm only interested in tracking logged on users)
Also WP2.7 based running on a Ubuntu 8.10 based server used solely for this blog
///P
Posted 3 years ago # -
I will investigate it, thank you for reporting
Posted 3 years ago # -
dream-
MemberI am experiencing severe slowdowns as well. WP 2.7, Apache server.
With the plugin deactivated a full page will load in a few seconds. With the plugin activated, it takes around 1 minute. There is a long delay before it even starts loading anything visually, the browser says "Waiting for mydomain.com..." and after the long delay it finally loads.
I do not have large traffic at all, it is a site under development, and do not use the widget.
The times when I have seen similar delays has been when trying to log into a mysql database from an outside host instead of doing it from the machine that hosts the mysql database. Probably something to do with reverse lookups. But I don't see how that could be the case here.
Any ideas?
Posted 2 years ago # -
I had this problem too, and what's causing it are the several calls made by Wassup to php's gethostbyaddr function which does the host lookup. The problem is at its worst if the function can't find the host name (ie. on a local LAN). To solve it, I basically changed every call to gethostbyaddr in wassup.php to call "gethost", which I've included below. This still uses gethostbyaddr, but it caches the calls on each run with a local cache and by using memcached (if enabled and available with the object-cache.php dropin). Ideally, it would probably be better to code an nslookup (for windows) or host call for linux, but for now this is working for me just fine. Another way would be to cache/store the host lookups in the database for a period of time. Hopefully the author of Wassup will look to include this patch (or some even better variation) in a future release. I believe the poor performance of this one function call is holding back the high potential of this plugin.
(I placed the function just below the "global $wp_version;" statement in wassup.php:
function gethost($ip) {
//much faster cached replacement for gethostbyaddr - http://us3.php.net/gethostbyaddr
global $dns_cache;
if ($dns_cache[$ip]) {
return $dns_cache[$ip];
} else {
if (!$dns = wp_cache_get( $ip, 'dns', 216000 ) ) {
$dns = gethostbyaddr($ip);
wp_cache_add( $ip, $dns, 'dns', 216000 );
}
$dns_cache[$ip] = $dns;
return $dns;
}
}_______________________________
Alexander - http://www.vlogolution.comPosted 2 years ago # -
I had this problem too, and what's causing it are the several calls made by Wassup to php's gethostbyaddr function which does the host lookup. The problem is at its worst if the function can't find the host name (ie. on a local LAN). To solve it, I basically changed every call to gethostbyaddr in wassup.php to call "gethost", which I've included below. This still uses gethostbyaddr, but it caches the calls on each run with a local cache and by using memcached (if enabled and available with the object-cache.php dropin). Ideally, it would probably be better to code an nslookup (for windows) or host call for linux, but for now this is working for me just fine. Another way would be to cache/store the host lookups in the database for a period of time. Hopefully the author of Wassup will look to include this patch (or some even better variation) in a future release. I believe the poor performance of this one function call is holding back the high potential of this plugin.
(I placed the function just below the "global $wp_version;" statement in wassup.php:
function gethost($ip) {
//much faster cached replacement for gethostbyaddr - http://us3.php.net/gethostbyaddr
global $dns_cache;
if ($dns_cache[$ip]) {
return $dns_cache[$ip];
} else {
if (!$dns = wp_cache_get( $ip, 'dns', 216000 ) ) {
$dns = gethostbyaddr($ip);
wp_cache_add( $ip, $dns, 'dns', 216000 );
}
$dns_cache[$ip] = $dns;
return $dns;
}
}_______________________________
Alexander - http://www.vlogolution.comPosted 2 years ago # -
Thank you Alexander, the patch is on testing and it looks good for the next release.
Posted 2 years ago #
Reply
You must log in to post.