I was referring to Xindice. I looked at XMLResourceImpl, and if it is anything to go by, then the memory consumption is understandable. There has also been some concern about collection.close() being a nil implemention (I asume it still is). The getContentAsSAX gets a new XMLReader for every call relying on the garbage collector and Xerxes for memory efficiency. That in itself might be quite a hit to my knowledge.
----- Original Message ----- From: "Alain Javier Guarnieri del Gesu" <[EMAIL PROTECTED]> To: "Henrik Vendelbo" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, November 01, 2003 6:03 PM Subject: Re: Other sticky issues > * Henrik Vendelbo <[EMAIL PROTECTED]> [2003-11-01 16:29]: > > ----- Original Message ----- > > From: "Alain Javier Guarnieri del Gesu" <[EMAIL PROTECTED]> > > To: <xindice-users@xml.apache.org>; <[EMAIL PROTECTED]> > > Sent: Thursday, October 30, 2003 1:50 PM > > Subject: Re: Predicates are ignored in Xindice XPATH? > > > > > > > * Kevin Ross <[EMAIL PROTECTED]> [2003-10-22 17:18]: > > > > > > > From: Kurt Kavanaugh [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, October 22, 2003 11:00 AM > > > > To: xindice-users@xml.apache.org > > > > Subject: RE: Predicates are ignored in Xindice XPATH? > > > > > > > > BTW- Has anyone from the xindice team ever contacted the saxon guys, to > > > > check on how their xquery might be integrated? I believe they may have > > > > licensing conflicts, but maybe the saxon group would be interested in > > > > adjusting the license for xindice use? (HINT: maybe this would solve the > > > > whole issue) > > > > Is there a roadmap for XQuery support? Besides aggregation across > > > documents, are the any other major sticking points in Xindice? > > > > What needs tweaking in the Saxon license? (IANAL) > > > Memory consumption is sticky in my book. It uses a huge amount of > > memory it seems from my tests. It could be the way I access, but > > it's fairly straightforward though. > > > Create an object through JAXB once. Then persist it to a Xindice > > collection 1000 times via SAX. That appears to use beyond 1Gb RAM > > according to java.lang.Runtime. And takes 17 secs. > > > Admitiably I do use a unit test that isn't very kind, since every > > time I run a test I create the collection, get the collection, do > > the test, and then remove all resources in the collection > > I've been reading the code for XQuery. They use WeakHashMaps to > cache the page hits. If the test runs fast enough, it doesn't seem > like there would be a need to collect that memory. Or perhaps, their > is a leak somewhere, meaning, that a pages are read over and over > again, and never dereferenced. > > -- > Alain Javier Guarnieri del Gesu - [EMAIL PROTECTED] > >
