= Proposal title =

|| '''Date''' || 2010/03/06 ||
|| '''Contact(s)''' || simonp ||
|| '''Last edited''' || [[Timestamp]] ||
|| '''Status''' || in progress, complete ||
|| '''Assigned to release''' || 2.5 ||
|| '''Resources''' || Not applicable ||

== Overview ==

A number of performance issues have been found when GN is applied to catalogs containing 10s of thousands of records:

- search speed: search speed appears to degrade badly with the size of the result set, ie. searches with large result sets were taking much longer than expected to process than searches with small result sets
- indexing speed: importing 10s of thousands of records via batch import, harvesters, massive operations and CSW transactions was taking too long eg. local file system harvest of 20k records was taking 10-12 hours...

=== Proposal Type ===
 * '''Type''': Core Change
 * '''App''': !GeoNetwork
 * '''Module''': Harvester, Kernel, Data Manager, Metadata Import, Lucene Index, Search results, Massive Operations and CSW Transaction support

=== Links ===
 * '''Documents''':
 * '''Email discussions''':
 * '''Other wiki discussions''':

=== Voting History ===
 * Vote proposed by X on Y, result was +/-n (m non-voting members).

----

== Motivations ==
Make GN perform better for catalogs with 10s of thousands of records.

== Proposal == 

Address the search speed issue:

=== Backwards Compatibility Issues ===

== Risks ==

== Participants ==
 * List of participants and role (if necessary) in current GIP