Avoiding problems using Tomcat at high-load indexes

Previous topic

eZ Find

Next topic

Author	Message
Jens Görisch	Wednesday 22 July 2009 10:24:25 am Hello, as the title may already suggest, I'm interested in using eZ Find (i.e. Solr) with a Tomcat servlet container. The reason for this are problems, when running the default setting (with Jetty). We have an index with overall more than 100k documents. After some time running, the Solr server runs into troubles. It doesn't update the index anymore (apparently COMMIT doesn't work) and a look into the log files reveals, that logging was stopped abruptly (i.e. the last log entry is incomplete). Also some compiled servlets are missing (e.g. <i>/solr/admin/registry.jsp</i>) and an exception is thrown, when the respective page is accessed. All this sounds for me like it is caused by the container. Now I'm very curious, if perhaps this happened to anyone else and thus about your experiences with such kind of behaviour. Also I would like to know, if you could make improvements by using tomcat (or perhaps another servlet container). Thanks in advance Jens Görisch

Author

Message

Jens Görisch

Wednesday 22 July 2009 10:24:25 am

Hello,

as the title may already suggest, I'm interested in using eZ Find (i.e. Solr) with a Tomcat servlet container.

The reason for this are problems, when running the default setting (with Jetty).

We have an index with overall more than 100k documents. After some time running, the Solr server runs into troubles. It doesn't update the index anymore (apparently COMMIT doesn't work) and a look into the log files reveals, that logging was stopped abruptly (i.e. the last log entry is incomplete). Also some compiled servlets are missing (e.g. <i>/solr/admin/registry.jsp</i>) and an exception is thrown, when the respective page is accessed.

All this sounds for me like it is caused by the container. Now I'm very curious, if perhaps this happened to anyone else and thus about your experiences with such kind of behaviour. Also I would like to know, if you could make improvements by using tomcat (or perhaps another servlet container).

Thanks in advance

Jens Görisch

eZ debug

Timing:	Jan 18 2025 10:19:02
Script start
Timing:	Jan 18 2025 10:19:02
Module start 'layout'
Timing:	Jan 18 2025 10:19:02
Module start 'content'
Timing:	Jan 18 2025 10:19:02
Module end 'content'
Timing:	Jan 18 2025 10:19:02
Script end

Main resources:

Total runtime	0.0176 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0068	588.1875	152.6563
Module start 'layout'	0.0068	0.0041	740.8438	39.5078
Module start 'content'	0.0110	0.0050	780.3516	86.2422
Module end 'content'	0.0159	0.0017	866.5938	30.3047
Script end	0.0176		896.8984

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	15.3199	14	0.0002
Check MTime	0.0013	7.3202	14	0.0001
Mysql Total
Database connection	0.0011	6.0332	1	0.0011
Mysqli_queries	0.0040	22.8039	3	0.0013
Looping result	0.0000	0.0920	1	0.0000
Template Total	0.0013	7.6	1	0.0013
Template load	0.0008	4.3483	1	0.0008
Template processing	0.0006	3.1898	1	0.0006
Override
Cache load	0.0005	2.7365	1	0.0005
General
dbfile	0.0003	1.5604	8	0.0000
String conversion	0.0000	0.0406	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs