OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



Improve performance on searching over all journals

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.

Improve performance on searching over all journals

Postby pkpsupport » Tue Jun 12, 2007 2:59 am

Is there anything we can do to improve performance when searching over all 250 journals? We loaded +/- 40 000 articles. I've checked that indexes are build in MYSQL. Our installation of OJS 2.1.1 is running on a linux server:

Linux zypher 2.6.17-11-server
processor : 7
cpu MHz : 3192.109

Response time on searching can be tested on:

http://ejournals.sabinet.co.za/index.php/index/search

Regards
Jacobien
pkpsupport
 
Posts: 16
Joined: Thu Sep 07, 2006 2:26 am
Location: Pretoria

Postby asmecher » Tue Jun 12, 2007 10:02 am

Hi Jacobien,

Searching is going to be an IO-limited operation, so make sure you focus your attention on that. From a couple of test searches, the performance looks acceptable to me; you may find that you're able to alter a few of the foreign key and primary key data types in the database to be smaller, which will also compact the indexes. If you have any database optimization experience, you may want to experiment with different storage engines and in-memory strategies.

At a certain number of records, a reverse MySQL index like the one used in OJS will start to degrade. We intend to assess Lucene in the future for possible integration with the Harvester application; if it turns out to be a straight-forward process we may offer it as an option in OCS and OJS. However, the current approach has performed fine for those applications in our experience thus far.

Regards,
asmecher
 
Posts: 8419
Joined: Wed Aug 10, 2005 12:56 pm


Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 3 guests