Just to add. I'm using Centos 4.1 but running and compiled pylucene
using the python 2.4.3 offical Fedora 3 (or the likes) rpm from
python.org. Centos/Rhel 4 comes with 2.3.X as the standard version.
Also using latest twisted package 2.0.1 with a 10 line Echo server as
the foundation for my lucene server. Very simple.
gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)
libgcj-devel-3.4.3-22.1
libgcj-3.4.3-22.1
My lucene+twisted server is serving real traffic with 5 to 10 queries
per second and the performance is fanstastic. Unfortunately the memory
problem is forcing me to write a script to kill/restart the daemon every
4 minutes.
Xing
[EMAIL PROTECTED] wrote:
Hi all,
I just coded a twisted + pylucene server. After having live query feeds
to the daemon, I notice the python server's memory just goes up and up.
After it reaches around 1.3GB of memory, I start to get
"GC Warning: Repeated allocation of very large block""
After a minute or two over the 2GB memory mark, I have 4GB memory rhel 4
with zero swap in use so memory is not the problem, the server dies with
"Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS"
I'm new to python. I tried adding gc.collect() at the end of the
searches and adding "del myvars" at the end as well before the
gc.collect(). Still memory goes up and up with no end in sight. The code
base is very small so not sure where the memory leaks are coming.
Thanks for any help.
Xing Li
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
