Home » forums » General » General Discussions

OutOfMemory problem

Submitted by Patrick Peccatte on Thu, 2007-07-05 01:29.General Discussions

Hi,
I am testing DBSight 1.4.3 with Jetty bundled on a XP Pro having 1GB RAM.
All was fine with 200.000 documents indexed.
Now I cannot do any search using an index with 1.500.000 documents indexed. Index size is 1.388 MB and of course I have configured Memory mode search as "Leave Index on disk".
I have tried to run Jetty server with different memory settings as described in the following Wiki page:
http://wiki.dbsight.com/index.php?title=OutOfMemory
without success...
All searches failed with message "OutOfMemoryError: Java heap space" on server console.
Any suggestion ?
--
Patrick Peccatte
www.softexperience.com

login or register to post comments | previous forum topic | next forum topic

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
check the memory status
Submitted by will on Thu, 2007-07-05 11:01.

You can check the memory status by going to

Dashboard => "System Report"(upper right corner) => "System Info" tab

I think you mean 1,388 MB, not 1.388 MB. :)

Some configuration may consume too much memories also. So if you still have those problems after increasing your memory to, say 640M, and it shows up correctly in "System Info" tab, you can send us the index configuration and let us try to tune it.

login or register to post comments
OutOfmemory problem
Submitted by Patrick Peccatte on Thu, 2007-07-05 13:19.

I have started the server with the following line:
java.exe -Xmx640m -XX:NewRatio=1 -jar start.jar
And now I see the following in "System info":
Total Memory 608.00 MB
Free Memory 19.68 MB
Max Memory 608.00 MB
Is it OK ?

I have also tested different MySQL drivers (2.0.14, 3.1.14, 5.0.6) with the same memory problem.

1.388 MB is French notation, sorry...
With best regards

login or register to post comments
Looks good
Submitted by will on Thu, 2007-07-05 16:33.

Maybe try to increase the memory a bit more.

The MySQL drivers should not matter here since they are used only for indexing, while your problem seems in searching.

You can send us the index configuration and let us help you to tune it.

Do you use "Keywords" a lot? It uses some more memory than other field types.

login or register to post comments
it works without keywords filterable
Submitted by Patrick Peccatte on Thu, 2007-07-05 20:57.

Yes I use keywords a lot (it is a picture database with many IPTC keywords). I have disabled "Filterable" check box in Search/Filterable colomns for this keywords column and it works, even with JVM set to 256M. But I have no chance to display NarrowBy feature now...
I have also learned that Database is not used for searching.
Also, I have tested with PostgreSQL 8.2 and indexing is much faster than with MySQL 5.0.
Thanks for your help

login or register to post comments
Increase Memory size if use Keywords a lot
Submitted by will on Fri, 2007-07-06 17:22.

Looks like you need to increase memory size more. Simple searching is relatively less memory hungry. But to do NarrowBy feature, a fast counting is needed. Leaving contents on disk is doable, but awfully slow. If you need NarrowBy, you do need more memory.

I also found PostgreSQL is better than MySQL in many ways...

login or register to post comments
Thanks
Submitted by Patrick Peccatte on Sat, 2007-07-07 10:52.

Thanks for explanations, Will

login or register to post comments