<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More Visitors, More Stats</title>
	<atom:link href="http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/feed/" rel="self" type="application/rss+xml" />
	<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=more-visitors-more-stats</link>
	<description>Mike Little&#039;s not-quite-so-daily thoughts, babblings, and random synapse firings!</description>
	<lastBuildDate>Sat, 04 Feb 2012 22:14:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TechniCool</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-193025</link>
		<dc:creator>TechniCool</dc:creator>
		<pubDate>Sat, 29 Jul 2006 21:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-193025</guid>
		<description>Online stats services like the paid Sitemeter are good and fairly fast. Watch out for awstats which had some serious security holes (recently). My server was compromised through this stats package.

Thanks TechniCool(Australia)</description>
		<content:encoded><![CDATA[<p>Online stats services like the paid Sitemeter are good and fairly fast. Watch out for awstats which had some serious security holes (recently). My server was compromised through this stats package.</p>
<p>Thanks TechniCool(Australia)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Smith</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-60969</link>
		<dc:creator>Richard Smith</dc:creator>
		<pubDate>Fri, 26 Aug 2005 16:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-60969</guid>
		<description>I havent been blogging very long, but I was running a web page from my home pc for a while, so I used to pay close attention just to the server logs, then added Nedstats, and then sitemeter, both free, but both add some more load time.</description>
		<content:encoded><![CDATA[<p>I havent been blogging very long, but I was running a web page from my home pc for a while, so I used to pay close attention just to the server logs, then added Nedstats, and then sitemeter, both free, but both add some more load time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spong Bo</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-60967</link>
		<dc:creator>Spong Bo</dc:creator>
		<pubDate>Fri, 26 Aug 2005 16:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-60967</guid>
		<description>Wow, you&#039;re actually the Technorati #1 blog (although their link pointed to zed1.com/ and I had to do some digging to get here). Congratulations!</description>
		<content:encoded><![CDATA[<p>Wow, you’re actually the Technorati #1 blog (although their link pointed to zed1.com/ and I had to do some digging to get here). Congratulations!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicola</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58998</link>
		<dc:creator>nicola</dc:creator>
		<pubDate>Fri, 12 Aug 2005 13:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58998</guid>
		<description>well i thought I would comment as I found your site through google and now have been reading, and let me say its been very entertaining, its like finding a needle in a haystack, finding a great readable blog!!!

thanks for making my night
hi and have a great day from Australia
xx Nicola</description>
		<content:encoded><![CDATA[<p>well i thought I would comment as I found your site through google and now have been reading, and let me say its been very entertaining, its like finding a needle in a haystack, finding a great readable blog!!!</p>
<p>thanks for making my night<br />
hi and have a great day from Australia<br />
xx Nicola</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58222</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 03 Aug 2005 19:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58222</guid>
		<description>PJ, 
Pphlogger doesn&#039;t do its analysis in real time, it merely logs the information obtained from the javascript routine (or what it can glean from the noscript image request) straight to the database. 

The analysis, collating statistics, putting together page history/visitor path, etc. is done after the fact when you view the various reports.</description>
		<content:encoded><![CDATA[<p>PJ,<br />
Pphlogger doesn’t do its analysis in real time, it merely logs the information obtained from the javascript routine (or what it can glean from the noscript image request) straight to the database. </p>
<p>The analysis, collating statistics, putting together page history/visitor path, etc. is done after the fact when you view the various reports.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJ Brunet</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58162</link>
		<dc:creator>PJ Brunet</dc:creator>
		<pubDate>Wed, 03 Aug 2005 02:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58162</guid>
		<description>Sorry I&#039;m not too familiar with this script--but I looked at the feature list...  Here are some things that could be slowing it down:

&quot;traceroutes by above.net&quot; This could be slowing it down--traceroutes can take some time.  You can probably do the traceroutes from your own server to speed things up,  but traceroute info isn&#039;t very useful anyway--maybe turn it off.  

Maybe shorten this timeout if it&#039;s more than 1 day by default. &quot;stores IP-adress+cookie to avoid multiple hits by the same user (you can set a timeout)&quot;  If this script runs in realtime, it could be wasting a lot of time scanning a big log file each time a new hit comes in.  If you&#039;re setting a cookie, why use a timeout at all?  If the surfer has your cookie already then don&#039;t count the hit as unique--simple--increment your raw count instead.  

&quot;visitor-path&quot; As with the previous feature, this code could be wasting a lot of time scanning the entire database over and over and over again matching IP&#039;s...  I&#039;m not sure if this runs in realtime or what, but off the top of my head--you could just keep the hit list sorted in a flat file, then as new hits come in, just go down the list in order...  if there&#039;s a cookie already, then search for a match, then drop it in.  In this manner, all the repeat visits will usually be right at the top of the list, saving a ton of search time...  and you would know ahead of time if this was a  repeat visit because you can test for the cookie before  doing anything, and if there&#039;s no cookie yet, set the cookie then add this hit to the top of your list in case they click something else...  in summary, keeping your hit lists sorted saves your script from having to do much searching at all.  I would imagine this is a lot faster than using mysql.</description>
		<content:encoded><![CDATA[<p>Sorry I’m not too familiar with this script–but I looked at the feature list…  Here are some things that could be slowing it down:</p>
<p>“traceroutes by above.net” This could be slowing it down–traceroutes can take some time.  You can probably do the traceroutes from your own server to speed things up,  but traceroute info isn’t very useful anyway–maybe turn it off.  </p>
<p>Maybe shorten this timeout if it’s more than 1 day by default. “stores IP-adress+cookie to avoid multiple hits by the same user (you can set a timeout)”  If this script runs in realtime, it could be wasting a lot of time scanning a big log file each time a new hit comes in.  If you’re setting a cookie, why use a timeout at all?  If the surfer has your cookie already then don’t count the hit as unique–simple–increment your raw count instead.  </p>
<p>“visitor-path” As with the previous feature, this code could be wasting a lot of time scanning the entire database over and over and over again matching IP’s…  I’m not sure if this runs in realtime or what, but off the top of my head–you could just keep the hit list sorted in a flat file, then as new hits come in, just go down the list in order…  if there’s a cookie already, then search for a match, then drop it in.  In this manner, all the repeat visits will usually be right at the top of the list, saving a ton of search time…  and you would know ahead of time if this was a  repeat visit because you can test for the cookie before  doing anything, and if there’s no cookie yet, set the cookie then add this hit to the top of your list in case they click something else…  in summary, keeping your hit lists sorted saves your script from having to do much searching at all.  I would imagine this is a lot faster than using mysql.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58160</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 02 Aug 2005 22:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58160</guid>
		<description>PJ, 
thanks for your comments. I think you are right that pphlogger should be able to cope. I remember &lt;a href=&quot;http://photomatt.net/2004/05/23/powerphlogger/&quot; rel=&quot;nofollow&quot;&gt;Matt dropped Power Pphlogger&lt;/a&gt; last year for performance reasons, but I don&#039;t imagine my traffic is anything like Matt&#039;s!
I know that my server is not optimized in any way. I should look at that too.</description>
		<content:encoded><![CDATA[<p>PJ,<br />
thanks for your comments. I think you are right that pphlogger should be able to cope. I remember <a href="http://photomatt.net/2004/05/23/powerphlogger/" rel="nofollow">Matt dropped Power Pphlogger</a> last year for performance reasons, but I don’t imagine my traffic is anything like Matt’s!<br />
I know that my server is not optimized in any way. I should look at that too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJ Brunet</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58157</link>
		<dc:creator>PJ Brunet</dc:creator>
		<pubDate>Tue, 02 Aug 2005 19:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58157</guid>
		<description>A typical virtual account with realtime PHP stats should  be able to manage 50k visitors/day without a problem--if  you are having difficulty with 25k/month, some sloppy spaghetti code could be the culprit, either that or MySQL is slowing you down--I personally prefer flat files, as does WebSideStory.</description>
		<content:encoded><![CDATA[<p>A typical virtual account with realtime PHP stats should  be able to manage 50k visitors/day without a problem–if  you are having difficulty with 25k/month, some sloppy spaghetti code could be the culprit, either that or MySQL is slowing you down–I personally prefer flat files, as does WebSideStory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58037</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Mon, 01 Aug 2005 20:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58037</guid>
		<description>Hi AJ,
Unfortunately, I also need to record more than just my blog pages, so a WP only stat package won&#039;t do. 

Thanks for all the suggestions folks, I&#039;m looking into a few different packages at the moment.

Mike</description>
		<content:encoded><![CDATA[<p>Hi AJ,<br />
Unfortunately, I also need to record more than just my blog pages, so a WP only stat package won’t do. </p>
<p>Thanks for all the suggestions folks, I’m looking into a few different packages at the moment.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ</title>
		<link>http://zed1.com/journalized/archives/2005/07/31/more-visitors-more-stats/comment-page-1/#comment-58031</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Mon, 01 Aug 2005 16:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://zed1.com/journalized/?p=1142#comment-58031</guid>
		<description>You might want to use WP-stattraq. Its a really nice tool which does not count the crawler/bot hits which Shortstat seems to include in the display.

It&#039;s available at 

&lt;a href=&quot;http://www.randypeterman.com/StatTraq/index.php&quot; rel=&quot;nofollow&quot;&gt;Wp-StatTraq&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>You might want to use WP-stattraq. Its a really nice tool which does not count the crawler/bot hits which Shortstat seems to include in the display.</p>
<p>It’s available at </p>
<p><a href="http://www.randypeterman.com/StatTraq/index.php" rel="nofollow">Wp-StatTraq</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

