a couple of issues with performance on our end. mostly wondering if this is
what i should expect for performance or not.
we have no <index> section currently defined in the config file, so full-text
indexing of all fields should be enabled.
- solaris 8 (intel) running on a 4-CPU dell server w/ 2GB ram.
- server.sh was modified to run with '-Xms128m -Xmx256m'.
- java 1.3.1.
indexing (using native database):
- my current test data set includes 5454 documents totalling about 48MB of
- indexing the first few hundred documents takes around 300-500ms per
- indexing gets progressively slower. the last documents typically take
10-12 secs per document.
- searching for full-text content is typically taking 30-45 secs. this seems
excessive for such a small dataset, although i may be indexing too much.
some of the server log info from the query.
2001-10-22 14:05:20,784 DEBUG> movie/%
2001-10-22 14:05:29,167 INFO > query: (child::media[(attribute::name='media.movie.14552505')])
2001-10-22 14:05:29,200 DEBUG> cache hit
*** what is cached? ***
2001-10-22 14:05:29,212 DEBUG> getChildren took 1
*** what happens here that is taking so much time (35+ secs)? ***
2001-10-22 14:06:04,995 INFO > getNodeIdsEqualTo took 6747
2001-10-22 14:06:04,995 INFO > found: 1
sorry, i'm not a java programmer. i'll take a look thru the src to try to
answer some of the above questions, but input from others would be greatly
Brad Burdick | bburdick@...
http://media.org/ | The medium is NOT the message