[phpOpenTracker-User] Speeding up OpenTracker Reporting

"Christopher Hogan" <[email protected]>
Newsgroups gmane.comp.web.phpopentracker.general
Message-ID <000001c37e02$bfb91cc0$9701a8c0@alice>
Hi there,

I'm using phpOpenTracker v1.2 as a logging engine for documents that I
track banner ad
hits on.  So for example I use a php page to prepend a string e.g.-

// log exit
	phpOpenTracker::log(  
		array(    
		'document' => 'My_String_'.$banner  
		)
	);

header("location: http://www.somewhere.com");

I wrote a php application that breaks down the data via each 'document'
string and displays every banner
associated with it.  It works great for tracking multiple campaigns
using many different banners pointing to different locations.  (thanks
to your open API) 

My only difficulty is now that I've been using it for a couple months
the reporting engine is running very slowly.  This includes the sample
reporting pages provided in phpOpenTracker when analyzing the same data.

I use MySQL version 3.23.52 with delay_key_write enabled.  This is a
dedicated database server;

The database currently holds:

TB: pot_accesslog              ROWS: 431,797     USED: 23.3 MB  
TB: pot_add_data               ROWS: 0           USED: 1.0 KB  
TB: pot_documents              ROWS: 148         USED: 16.6 KB  
TB: pot_exit_targets           ROWS: 402         USED: 18.8 KB  
TB: pot_hostnames              ROWS: 46,624      USED: 1.7 MB  
TB: pot_operating_systems      ROWS: 24          USED: 2.6 KB  
TB: pot_referers               ROWS: 101,992     USED: 13.8 MB  
TB: pot_user_agents            ROWS: 44          USED: 3.1 KB  
TB: pot_visitors               ROWS: 332,631     USED: 29.5 MB

Additional information: PHP 4.3.3

I've noted that by dropping the table indexes speed increases are
possible:

" you might want to trade the speed of the phpOpenTracker API for an
increased performance of the phpOpenTracker Logging Engine by dropping
the table's indexes."

However which table indexes should I drop?  By "phpOpenTracker API" do
you mean the reporting mechanism?  Reporting is where I need the speed
to increase.  

I can set up a development environment to test different techniques but
I'd prefer not to see a performance decrease in the logging engine as it
is important that this also runs fast.

I've looked into MERGE tables however I'm a bit unsure of how to set
something like this up for opentracker; is it possible that someone
could provide me with an example?  Would this increase the speed of
reporting or just logging?

Are there any other simple, effective methods of increasing the
reporting speed of OpenTracker?

Thanks in Advance,
I love every other aspect of your program!

Christopher Hogan




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.