1. I have ported (see attach) my example with threads to Java... and it works! on 50Gb index.
That's excellent news.
As I was following the various threads on [EMAIL PROTECTED] yesterday, Hans Boehm seemed to hint something about 1gb or 3gb heap size limits. I wasn't sure of what he meant.
http://gcc.gnu.org/ml/java/2005-02/msg00181.html
It seems that large heaps can be a problem for libgcj applications and may require custom builds of recent gcj for resolution. This is going to take some experimenting.
So, where do we go from here ?
Andi..
So, it seems like pure Java works fine.
2. Also I have tried to run PyLucene source with environment GC_PRINT_STATS=1 as Boehm, Hans has suggested. I received following log of messages (gc.log). Please, check it. Maybe it will give you ideas...
3. Also I have tried 'export GC_FIND_LEAK=1'. Program shown some messages. I hope this will give us ideas.
Leaked composite object at start: 0x82f69d0, appr. length: 16 ... Leaked composite object at start: 0x82f6d60, appr. length: 16 Leaked atomic object at start: 0x82f5f50, appr. length: 112 Leaked composite object at start: 0x82f4fb0, appr. length: 16 Leaked composite object at start: 0x82f4fc0, appr. length: 16 Leaked composite object at start: 0x82f4ff0, appr. length: 16 Leaked atomic object at start: 0x82f1500, appr. length: 80 ... Leaked composite object at start: 0x82c12d0, appr. length: 80 Leaked atomic object at start: 0x8293fa8, appr. length: 8 ... Leaked atomic object at start: 0x8293fd8, appr. length: 8 Leaked composite object at start: 0x826c930, appr. length: 24 ... Leaked composite object at start: 0x82462d0, appr. length: 24
Yura Smolsky.
_______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
