OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



COUNTER Statistics: freezes - to much data?

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

COUNTER Statistics: freezes - to much data?

Postby elbaek » Thu Mar 22, 2007 7:49 am

Hi

We have experienced that our COUNTER statistics freezes. We have 4 active journals in the same OJS instalation and some 14.000 views per month. My best guess is that the freeze occoured when we hit 40.000 or 50.000 views and we didn't clear the log.

We have now cleared the log via PHP. But is there a upper limit to the capacity of the log?

Our plan now is to clear the log once a month. But it would have been a better service for our journals if we could have presented the complete statistics in the Journal Manager pages.

Best regards

Mikael K. Elbaek
Ejournals@cbs
Copenhagen Business School
elbaek
 
Posts: 13
Joined: Wed Jun 22, 2005 1:51 am
Location: Denmark

Postby asmecher » Thu Mar 22, 2007 10:58 am

Hi Mikael,

The current log parsing and report generation process is not particularly efficient, and that is something we'll be addressing in a future release. However, even mature analysis tools like Webalizer do require a significant amount of time to run. I suspect we'll move to a batch process in the future to best accommodate larger log files.

Note that the process of logging visitors is not a problem; it is fast and doesn't depend on the size of the log file. It's only the process of analysis that takes time and memory. You may find that increasing your memory and processing time limits in php.ini allows you to analyze bigger log files. Different releases of PHP (e.g. 4.x vs. 5.x) also behave very differently in terms of performance and memory usage with objects; in my experience, 5.x is significantly better.

Regards,
Alec Smecher
Open Journal Systems Team
---
Don't miss the First International PKP Scholarly Publishing Conference
July 11 - 13, 2007, Vancouver, BC, Canada
http://ocs.sfu.ca/pkp2007/
asmecher
 
Posts: 8903
Joined: Wed Aug 10, 2005 12:56 pm


Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 5 guests