Hi Ilias
I see your GeoNetwork instance has 1.5 Gb assigned, but also almost 512 Mb of free memory. I don’t think the memory is the issue, as 1.5 Gb should be enough.
If you use the UI for searches, it works fast? It’s only about CSW?
In any case sending your mail to the dev list, so other developers can check if any other stuff can be check to improve the performance in your system.
Regards,
Jose García
···
On Thu, Jul 20, 2017 at 2:43 AM, Kate Roberts <kate.roberts@anonymised.com> wrote:
Hi Ilias,
I’m not a programmer, but just wanted to support Jose’s statement wrt GeoNetwork’s typical CSW performance.
You might want to forward this email to the GN-dev group?
Kate
From: ilias ioannou [mailto:illiasi@anonymised.com]
Sent: Wednesday, 19 July 2017 7:26 PM
To: Kate Roberts
Subject: Re: [GeoNetwork-devel] CSW vs OpenSearch [SEC=UNCLASSIFIED]Dear all,
the geonetwork has 32406 records, it is residing in a server with 16GB RAM and it is configured to store the spatial_index in Postgres.
The problem is that it is not the only process residing in the server and GN is struggling and needs more RAM.
I get this from the SYSTEM INFORMATION in the admin section of GN:
JVM version
1.8.0_131
System architecture
amd64
JVM name
OpenJDK 64-Bit Server VM
System name
Linux
Total free memory
489804
JVM vendor
Oracle Corporation
Total memory
1495808
XSLT factory
de.fzi.dbs.xml.transform.CachingTransformerFactoryWhat kind of optimizations could i do? Should i change something in settings? Is RAM the problem?
Thanx for your time.
From: Kate Roberts <kate.roberts@anonymised.com>
Sent: Tuesday, July 18, 2017 12:42 AM
To: Jose Garcia; ilias ioannou
Cc: geonetwork-devel@anonymised.comsourceforge.net; Kate Roberts
Subject: RE: [GeoNetwork-devel] CSW vs OpenSearch [SEC=UNCLASSIFIED]Hi Ilias and Jose,
I agree that 4 mins is very unusual
We run GeoNetwork v.2.10, and on our instance, using CSW, returning 100 records takes < 4 seconds.
For instance: this WCAG-compliant GUI [ http://www.bom.gov.au/metadata/catalogue/index.shtml ] uses CSW to query our “externally-facing” GeoNetwork instance, with a postgres database. That instance only has 140 records in it.
We get similar CSW speeds with our “internally-facing” GeoNetwork instance – which has about 200,000 records in it.
HTH,
Kate
( kate.roberts@anonymised.com.157… )
From: Jose Garcia [mailto:jose.garcia@anonymised.com]
Sent: Tuesday, 18 July 2017 12:51 AM
To: ilias ioannou
Cc: geonetwork-devel@anonymised.comsourceforge.net
Subject: Re: [GeoNetwork-devel] CSW vs OpenSearchHi
100 records in 4 min is really bad performance and should not be usual. Can you provide some information about the setup you have and also the number of metadata in the catalogue?
Regards,
Jose García
On Mon, Jul 17, 2017 at 3:35 PM, ilias ioannou <illiasi@anonymised.com153…> wrote:
Dear all,
I am involved in a project where we have to retrieve information from a Geonetwork metadata catalog and display them to the user (not by using the native interface of GN).
We initially chose to implement the solution of CSW since it is highly reccomended by ESA and other european organizations. The problem is that CSW requests have a very bad performance and they have caused serious issues of usability (aka returning 100 records in 4 mins).
On the other hand we have noticed that the native UI of GN is still a very fast search engine (it uses opensearch protocol?), and by now we are considering to change all the implementation and never use CSW again.
Can someone explain me what is going on, and/or give me any suggestions?
Is it the lack of resources or optimizations? And if thats the reason, then why the native search engine stills works very fast?Kind regards,
ilias
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork–
Vriendelijke groeten / Kind regards,
Jose García
Veenderweg 13
6721 WD Bennekom
The Netherlands
T: +31 (0)318 416664
Please consider the environment before printing this email.
–
Vriendelijke groeten / Kind regards,
Jose García
Veenderweg 13
6721 WD Bennekom
The Netherlands
T: +31 (0)318 416664
Please consider the environment before printing this email.