[GeoNetwork-users] Load testing GN 2.6.4 shows memory leak

Hi all,

I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
At the same time I monitor the Tomcat process with JVisualVM (mostly
v1.6.0_30).
In JMeter I send the following request:
http://hostname/geonetwork/srv/en?any=iso
with 50 threads, 60 seconds ramp-up and 50 loops.

Some Java params for Tomcat:
-Xms500m -Xmx1g -server -XX:MaxPermSize=256m

The first 1000-1500 requests performs well, but after 2000 requests the memory
is almost eaten up and most time is spent in garbage collection.
(with -Xmx8g I can reach 19000 requests)

I have tested and found the same behaviour with the following configurations:
- JDK 1.7.0_01 and apache-tomcat-7.0.22
- JDK 1.6.0_30 and apache-tomcat-6.0.35
- JDK 1.5.0_22 and apache-tomcat-5.5.34

In the heap dump I find a lot of instances of
org.jdom.Element/Attribute/AttributeList/ElementList
so maybe GeoNetwork XML responses are eating memory.

I have also had a look at the configuration and tips in Mastering Adv.
Geonetwork:
http://geonetwork-
opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf

Many national and international institutions are using GeoNetwork, so I assume
there is a known stable configuration for GeoNetwork out there.
Please advice.

I will continue my load testing, maybe with Jetty.

merry christmas and happy new year from
Jørn Vegard Røsnes

The correct URL for my load testing is
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:

Hi all,

I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
At the same time I monitor the Tomcat process with JVisualVM (mostly
v1.6.0_30).
In JMeter I send the following request:

http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

with 50 threads, 60 seconds ramp-up and 50 loops.

Some Java params for Tomcat:
-Xms500m -Xmx1g -server -XX:MaxPermSize=256m

The first 1000-1500 requests performs well, but after 2000 requests the
memory is almost eaten up and most time is spent in garbage collection.
(with -Xmx8g I can reach 19000 requests)

I have tested and found the same behaviour with the following
configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
- JDK 1.6.0_30 and apache-tomcat-6.0.35
- JDK 1.5.0_22 and apache-tomcat-5.5.34

In the heap dump I find a lot of instances of
org.jdom.Element/Attribute/AttributeList/ElementList
so maybe GeoNetwork XML responses are eating memory.

I have also had a look at the configuration and tips in Mastering Adv.
Geonetwork:
http://geonetwork-
opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf

Many national and international institutions are using GeoNetwork, so I
assume there is a known stable configuration for GeoNetwork out there.
Please advice.

I will continue my load testing, maybe with Jetty.

merry christmas and happy new year from
Jørn Vegard Røsnes
---------------------------------------------------------------------------
--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
complex infrastructure or vast IT resources to deliver seamless, secure
access to virtual desktops. With this all-in-one solution, easily deploy
virtual desktops for less than the cost of PCs and save 60% on VDI
infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hi Jørn

About the tests, some comments. Although for sure require to check about
the memory issues.

1) xml.search is not a service used in GUI (as far as I know) and no very
good to use as doesn't paginate results (documentation about this service
seem wrong about this), so if your query returns for example 10000 records,
all are returned in response, not very handy for performance and memory.

In GUI instead is used main.search or main.search.embedded, that paginates
results. I would try with it instead for the tests. And possibly is a good
idea to disable xml.search service if you have a big catalog.

2) Make sure to add a HTTP Cookie manager, to reuse sessions in each thread
requests otherwise you'll get a new session per request done.

Will try to test tomorrow to provide feedback. Also I did some tests for
another project as got a similar issue using WebSphere, removing the cache
of regions in LuceneSearcher seemed better, but need to investigate this a
bit more.

Regards,
Jose García

On Thu, Dec 29, 2011 at 1:30 PM, Jørn Vegard Røsnes <jorn@anonymised.com>wrote:

The correct URL for my load testing is
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:
> Hi all,
>
> I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
> At the same time I monitor the Tomcat process with JVisualVM (mostly
> v1.6.0_30).
> In JMeter I send the following request:
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso
> with 50 threads, 60 seconds ramp-up and 50 loops.
>
> Some Java params for Tomcat:
> -Xms500m -Xmx1g -server -XX:MaxPermSize=256m
>
> The first 1000-1500 requests performs well, but after 2000 requests the
> memory is almost eaten up and most time is spent in garbage collection.
> (with -Xmx8g I can reach 19000 requests)
>
> I have tested and found the same behaviour with the following
> configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
> - JDK 1.6.0_30 and apache-tomcat-6.0.35
> - JDK 1.5.0_22 and apache-tomcat-5.5.34
>
> In the heap dump I find a lot of instances of
> org.jdom.Element/Attribute/AttributeList/ElementList
> so maybe GeoNetwork XML responses are eating memory.
>
> I have also had a look at the configuration and tips in Mastering Adv.
> Geonetwork:
> http://geonetwork-
>
opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf
>
>
> Many national and international institutions are using GeoNetwork, so I
> assume there is a known stable configuration for GeoNetwork out there.
> Please advice.
>
> I will continue my load testing, maybe with Jetty.
>
> merry christmas and happy new year from
> Jørn Vegard Røsnes
>
---------------------------------------------------------------------------
>--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
> complex infrastructure or vast IT resources to deliver seamless, secure
> access to virtual desktops. With this all-in-one solution, easily deploy
> virtual desktops for less than the cost of PCs and save 60% on VDI
> infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hi

Related to my previous mail, sorry seem I was not accurate about xml.search
service: It uses pagination if provided from/to parameters in request, but
if not provided all results are returned, what can be quite huge depending
on the catalogue size.

Maybe an improvement to avoid returning very long results can be limit
response to maximum number of results or so.

Also Francois provided feedback that seem used in GeoNetwork harvester, so
no a good idea to disable.

Regards,
Jose García

On Mon, Jan 2, 2012 at 4:59 PM, jose garcia <josegar74@anonymised.com> wrote:

Hi Jørn

About the tests, some comments. Although for sure require to check about
the memory issues.

1) xml.search is not a service used in GUI (as far as I know) and no very
good to use as doesn't paginate results (documentation about this service
seem wrong about this), so if your query returns for example 10000 records,
all are returned in response, not very handy for performance and memory.

In GUI instead is used main.search or main.search.embedded, that paginates
results. I would try with it instead for the tests. And possibly is a good
idea to disable xml.search service if you have a big catalog.

2) Make sure to add a HTTP Cookie manager, to reuse sessions in each
thread requests otherwise you'll get a new session per request done.

Will try to test tomorrow to provide feedback. Also I did some tests for
another project as got a similar issue using WebSphere, removing the cache
of regions in LuceneSearcher seemed better, but need to investigate this a
bit more.

Regards,
Jose García

On Thu, Dec 29, 2011 at 1:30 PM, Jørn Vegard Røsnes <jorn@anonymised.com>wrote:

The correct URL for my load testing is
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:
> Hi all,
>
> I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
> At the same time I monitor the Tomcat process with JVisualVM (mostly
> v1.6.0_30).
> In JMeter I send the following request:
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso
> with 50 threads, 60 seconds ramp-up and 50 loops.
>
> Some Java params for Tomcat:
> -Xms500m -Xmx1g -server -XX:MaxPermSize=256m
>
> The first 1000-1500 requests performs well, but after 2000 requests the
> memory is almost eaten up and most time is spent in garbage collection.
> (with -Xmx8g I can reach 19000 requests)
>
> I have tested and found the same behaviour with the following
> configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
> - JDK 1.6.0_30 and apache-tomcat-6.0.35
> - JDK 1.5.0_22 and apache-tomcat-5.5.34
>
> In the heap dump I find a lot of instances of
> org.jdom.Element/Attribute/AttributeList/ElementList
> so maybe GeoNetwork XML responses are eating memory.
>
> I have also had a look at the configuration and tips in Mastering Adv.
> Geonetwork:
> http://geonetwork-
>
opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf
>
>
> Many national and international institutions are using GeoNetwork, so I
> assume there is a known stable configuration for GeoNetwork out there.
> Please advice.
>
> I will continue my load testing, maybe with Jetty.
>
> merry christmas and happy new year from
> Jørn Vegard Røsnes
>
---------------------------------------------------------------------------
>--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
> complex infrastructure or vast IT resources to deliver seamless, secure
> access to virtual desktops. With this all-in-one solution, easily deploy
> virtual desktops for less than the cost of PCs and save 60% on VDI
> infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hi Jose and the mailing list,

we utilize the xml.search service for B2B communication.
main.search seems to only return HTML, and not so suitable for B2B.

Thanks for the tip about pagination, but I think it will only postpone the server crash.

Right now I'm trying to setup NetBeans 7, Tomcat and GeoNetwork for more detailed memory profiling.
I hope to find the source of the memory leak.
Also tried Eclipse TPTP 4.7.2, no success so far. (http://www.eclipse.org/tptp/)

kind regards
Jørn Vegard

Den 02.01.2012 16:59, skrev jose garcia:

Hi Jørn

About the tests, some comments. Although for sure require to check about the memory issues.

1) xml.search is not a service used in GUI (as far as I know) and no very good to use as doesn't paginate results (documentation about this service seem wrong about this), so if your query returns for example 10000 records, all are returned in response, not very handy for performance and memory.

In GUI instead is used main.search or main.search.embedded, that paginates results. I would try with it instead for the tests. And possibly is a good idea to disable xml.search service if you have a big catalog.

2) Make sure to add a HTTP Cookie manager, to reuse sessions in each thread requests otherwise you'll get a new session per request done.

Will try to test tomorrow to provide feedback. Also I did some tests for another project as got a similar issue using WebSphere, removing the cache of regions in LuceneSearcher seemed better, but need to investigate this a bit more.

Regards,
Jose García

On Thu, Dec 29, 2011 at 1:30 PM, Jørn Vegard Røsnes <jorn@anonymised.com <mailto:jorn@anonymised.com>> wrote:

    The correct URL for my load testing is
    http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

    On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:
    > Hi all,
    >
    > I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
    > At the same time I monitor the Tomcat process with JVisualVM (mostly
    > v1.6.0_30).
    > In JMeter I send the following request:
    http://localhost:8080/geonetwork/srv/en/xml.search?any=iso
    > with 50 threads, 60 seconds ramp-up and 50 loops.
    >
    > Some Java params for Tomcat:
    > -Xms500m -Xmx1g -server -XX:MaxPermSize=256m
    >
    > The first 1000-1500 requests performs well, but after 2000
    requests the
    > memory is almost eaten up and most time is spent in garbage
    collection.
    > (with -Xmx8g I can reach 19000 requests)
    >
    > I have tested and found the same behaviour with the following
    > configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
    > - JDK 1.6.0_30 and apache-tomcat-6.0.35
    > - JDK 1.5.0_22 and apache-tomcat-5.5.34
    >
    > In the heap dump I find a lot of instances of
    > org.jdom.Element/Attribute/AttributeList/ElementList
    > so maybe GeoNetwork XML responses are eating memory.
    >
    > I have also had a look at the configuration and tips in
    Mastering Adv.
    > Geonetwork:
    > http://geonetwork-
    >
    opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf
    <http://opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf&gt;
    >
    > Many national and international institutions are using
    GeoNetwork, so I
    > assume there is a known stable configuration for GeoNetwork out
    there.
    > Please advice.
    >
    > I will continue my load testing, maybe with Jetty.
    >
    > merry christmas and happy new year from
    > Jørn Vegard Røsnes
    >
    ---------------------------------------------------------------------------
    >--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
    > complex infrastructure or vast IT resources to deliver seamless,
    secure
    > access to virtual desktops. With this all-in-one solution,
    easily deploy
    > virtual desktops for less than the cost of PCs and save 60% on VDI
    > infrastructure costs. Try it free!
    http://p.sf.net/sfu/Citrix-VDIinabox
    > _______________________________________________
    > GeoNetwork-users mailing list
    > GeoNetwork-users@lists.sourceforge.net
    <mailto:GeoNetwork-users@lists.sourceforge.net>
    > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
    > GeoNetwork OpenSource is maintained at
    > http://sourceforge.net/projects/geonetwork

    ------------------------------------------------------------------------------
    Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
    complex
    infrastructure or vast IT resources to deliver seamless, secure
    access to
    virtual desktops. With this all-in-one solution, easily deploy virtual
    desktops for less than the cost of PCs and save 60% on VDI
    infrastructure
    costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
    _______________________________________________
    GeoNetwork-users mailing list
    GeoNetwork-users@lists.sourceforge.net
    <mailto:GeoNetwork-users@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geonetwork-users
    GeoNetwork OpenSource is maintained at
    http://sourceforge.net/projects/geonetwork

--
vennlig hilsen
Jørn-Vegard Røsnes
http://www.spacetec.no

Hi all,

it helps a lot to use HTTP Cookie Manager in JMeter.
We had a bad test.

kind regards
Jørn Vegard

Den 02.01.2012 16:59, skrev jose garcia:

Hi Jørn

About the tests, some comments. Although for sure require to check about the memory issues.

1) xml.search is not a service used in GUI (as far as I know) and no very good to use as doesn't paginate results (documentation about this service seem wrong about this), so if your query returns for example 10000 records, all are returned in response, not very handy for performance and memory.

In GUI instead is used main.search or main.search.embedded, that paginates results. I would try with it instead for the tests. And possibly is a good idea to disable xml.search service if you have a big catalog.

2) Make sure to add a HTTP Cookie manager, to reuse sessions in each thread requests otherwise you'll get a new session per request done.

Will try to test tomorrow to provide feedback. Also I did some tests for another project as got a similar issue using WebSphere, removing the cache of regions in LuceneSearcher seemed better, but need to investigate this a bit more.

Regards,
Jose García

On Thu, Dec 29, 2011 at 1:30 PM, Jørn Vegard Røsnes <jorn@anonymised.com <mailto:jorn@anonymised.com>> wrote:

    The correct URL for my load testing is
    http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

    On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:
    > Hi all,
    >
    > I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
    > At the same time I monitor the Tomcat process with JVisualVM (mostly
    > v1.6.0_30).
    > In JMeter I send the following request:
    http://localhost:8080/geonetwork/srv/en/xml.search?any=iso
    > with 50 threads, 60 seconds ramp-up and 50 loops.
    >
    > Some Java params for Tomcat:
    > -Xms500m -Xmx1g -server -XX:MaxPermSize=256m
    >
    > The first 1000-1500 requests performs well, but after 2000
    requests the
    > memory is almost eaten up and most time is spent in garbage
    collection.
    > (with -Xmx8g I can reach 19000 requests)
    >
    > I have tested and found the same behaviour with the following
    > configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
    > - JDK 1.6.0_30 and apache-tomcat-6.0.35
    > - JDK 1.5.0_22 and apache-tomcat-5.5.34
    >
    > In the heap dump I find a lot of instances of
    > org.jdom.Element/Attribute/AttributeList/ElementList
    > so maybe GeoNetwork XML responses are eating memory.
    >
    > I have also had a look at the configuration and tips in
    Mastering Adv.
    > Geonetwork:
    > http://geonetwork-
    >
    opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf
    <http://opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf&gt;
    >
    > Many national and international institutions are using
    GeoNetwork, so I
    > assume there is a known stable configuration for GeoNetwork out
    there.
    > Please advice.
    >
    > I will continue my load testing, maybe with Jetty.
    >
    > merry christmas and happy new year from
    > Jørn Vegard Røsnes
    >
    ---------------------------------------------------------------------------
    >--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
    > complex infrastructure or vast IT resources to deliver seamless,
    secure
    > access to virtual desktops. With this all-in-one solution,
    easily deploy
    > virtual desktops for less than the cost of PCs and save 60% on VDI
    > infrastructure costs. Try it free!
    http://p.sf.net/sfu/Citrix-VDIinabox
    > _______________________________________________
    > GeoNetwork-users mailing list
    > GeoNetwork-users@lists.sourceforge.net
    <mailto:GeoNetwork-users@lists.sourceforge.net>
    > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
    > GeoNetwork OpenSource is maintained at
    > http://sourceforge.net/projects/geonetwork

    ------------------------------------------------------------------------------
    Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
    complex
    infrastructure or vast IT resources to deliver seamless, secure
    access to
    virtual desktops. With this all-in-one solution, easily deploy virtual
    desktops for less than the cost of PCs and save 60% on VDI
    infrastructure
    costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
    _______________________________________________
    GeoNetwork-users mailing list
    GeoNetwork-users@lists.sourceforge.net
    <mailto:GeoNetwork-users@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geonetwork-users
    GeoNetwork OpenSource is maintained at
    http://sourceforge.net/projects/geonetwork

--
vennlig hilsen
Jørn-Vegard Røsnes
http://www.spacetec.no

Hi Jørn

Using a HTTP Cookie Manager seem a more realistic test indeed. Also check
about default session timeout in defined in web.xml. I think default is 180
minutes, that seem too much also, normally 20 minutes to expire inactive
sessions should be enough.

Independent of this doing some additional testing it, to check no memory
lock or so in the xml.search service.

Regards,
Jose García

On Tue, Jan 3, 2012 at 2:41 PM, Jørn-Vegard Røsnes <jorn@anonymised.com> wrote:

Hi all,

it helps a lot to use HTTP Cookie Manager in JMeter.
We had a bad test.

kind regards
Jørn Vegard

Den 02.01.2012 16:59, skrev jose garcia:

Hi Jørn

About the tests, some comments. Although for sure require to check about
the memory issues.

1) xml.search is not a service used in GUI (as far as I know) and no
very good to use as doesn't paginate results (documentation about this
service seem wrong about this), so if your query returns for example 10000
records, all are returned in response, not very handy for performance and
memory.

In GUI instead is used main.search or main.search.embedded, that
paginates results. I would try with it instead for the tests. And possibly
is a good idea to disable xml.search service if you have a big catalog.

2) Make sure to add a HTTP Cookie manager, to reuse sessions in each
thread requests otherwise you'll get a new session per request done.

Will try to test tomorrow to provide feedback. Also I did some tests for
another project as got a similar issue using WebSphere, removing the cache
of regions in LuceneSearcher seemed better, but need to investigate this a
bit more.

Regards,
Jose García

On Thu, Dec 29, 2011 at 1:30 PM, Jørn Vegard Røsnes <jorn@anonymised.com>wrote:

The correct URL for my load testing is
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso

On Thursday 29 December 2011 12:46:02 pm Jørn Vegard Røsnes wrote:
> Hi all,
>
> I'm load testing GeoNetwork 2.6.4 with JMeter 2.5.1.
> At the same time I monitor the Tomcat process with JVisualVM (mostly
> v1.6.0_30).
> In JMeter I send the following request:
http://localhost:8080/geonetwork/srv/en/xml.search?any=iso
> with 50 threads, 60 seconds ramp-up and 50 loops.
>
> Some Java params for Tomcat:
> -Xms500m -Xmx1g -server -XX:MaxPermSize=256m
>
> The first 1000-1500 requests performs well, but after 2000 requests the
> memory is almost eaten up and most time is spent in garbage collection.
> (with -Xmx8g I can reach 19000 requests)
>
> I have tested and found the same behaviour with the following
> configurations: - JDK 1.7.0_01 and apache-tomcat-7.0.22
> - JDK 1.6.0_30 and apache-tomcat-6.0.35
> - JDK 1.5.0_22 and apache-tomcat-5.5.34
>
> In the heap dump I find a lot of instances of
> org.jdom.Element/Attribute/AttributeList/ElementList
> so maybe GeoNetwork XML responses are eating memory.
>
> I have also had a look at the configuration and tips in Mastering Adv.
> Geonetwork:
> http://geonetwork-
>
opensource.org/_static/foss4g2010/FOSS4G_Mastering_Advanced_GeoNetwork.pdf
>
>
> Many national and international institutions are using GeoNetwork, so I
> assume there is a known stable configuration for GeoNetwork out there.
> Please advice.
>
> I will continue my load testing, maybe with Jetty.
>
> merry christmas and happy new year from
> Jørn Vegard Røsnes
>
---------------------------------------------------------------------------
>--- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
> complex infrastructure or vast IT resources to deliver seamless,
secure
> access to virtual desktops. With this all-in-one solution, easily deploy
> virtual desktops for less than the cost of PCs and save 60% on VDI
> infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
vennlig hilsen
Jørn-Vegard Røsneshttp://www.spacetec.no