RE: [phpOpenTracker-User] Speeding up OpenTracker Reporting

This is the same problem I'm experiencing.  Our production site ranked
23,021 page views today so far, and the only way I've been able to
generate reports is via custom code.

e.g.-

$start = mktime(0, 0, 0, $current_month, 1, $current_year);
$end   = mktime(0, 0, 0, $current_month, $last_day, $current_year);

$document = phpOpenTracker::get(  
array( 
   "api_call"    => "page_impressions",
   "constraints" => array ( 
      "document" => $campaign."_".$ad 
      ),
   "start"       => $start,
   "end"         => $end
));

But on campaigns where document exceeds 20,000 for the month, generating
a list of all the ads in the time frame takes more than 2 minutes.

I would think that scalability upgrades, documentation, and benchmarks
should be a top priority for OpenTracker so that people running sites
like these don't have to resort to WebTrends.

I've had to delete the database 5 times in the past 2 months to keep her
running.  Archiving static reports is not fun either.

:/

Christopher Hogan
perl -pe tr/a-zA-Z/n-za-mN-ZA-M/ 
[email protected]

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Jean-Christian Imbeault
Sent: Wednesday, September 24, 2003 7:14 PM
To: [email protected]
Subject: Re: [phpOpenTracker-User] Speeding up OpenTracker Reporting

? wrote:
>
> * It would be very usefull to archive old data to increase speed of 
> reports.

I agree that would be a good thing to have. But I think that finding a
way to make data retrieval faster is also just as important.

> The site I track with phpOpenTracker now got about 380.000 access_log 
> entries in 5 months.
> It needs more than 2 minutes time to generate the "Total Statistics" 
> report.

I know what you mean. Imagine a site that gets > 10,000 log entries a
day ... After a few months it becomes impossible to generate the report.

Does anyone here use phpOpenTracker on a production site that gets a
large amount of hits (>10K hits)? I am starting to worry that
phpOpenTracker does not scale well.

> * Idea for the example "simple_report": many users don't need all the 
> "Total Statisics" every time they enter phpOpenTracker.
> A less time consuming report as "start"-page which shows all aviliable

> months but not the other report sections. This gives the user the 
> chanche to navigate to a certain month more quickly.

Sure. You can write one yourself too, it's not that hard. I have written
a GUI front end to phpOpentracker to let you choose which report and for
what time period. I'll be happy to post the code.

Jean-Christian Imbeault



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Phpopencounter-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/phpopencounter-user





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf