Hi Dirk,Ok, thanks for the trick, that should work. The only point is that it should be less user friendly for developing than using the eclipse IDE, since I will have to set up the BaseX repo first of running a query.2014-09-26 12:11 GMT+02:00 Dirk Kirsten <dk@basex.org>:Hi Jean-Marc,
I guess you set it up using the standalone version? Could you maybe test using the Client/Server set-up. You could then test with a plain BaseXClient and the eclipse environment. As they both should access the same BaseXServer, there shouldn't be any difference in execution.
But I don't know what XQDT is doing internally and I would pretty much guess the error is somewhere there (because plain BaseX seems to execute just fine). As the development seems to have pretty much stalled, I am not sure we can do much about that...
On 09/26/2014 11:54 AM, jean-marc Mercier wrote:
> Hi Dirk,
>
> Thanks for your answer. I am setting up eclipse indigo, following the
> step-up procedure http://docs.basex.org/wiki/Integrating_Eclipse. The only
> difference is that I set using -Xmx12G as Interpreter Arguments.
>
> Cheers
>
>
> 2014-09-26 11:44 GMT+02:00 Dirk Kirsten <dk@basex.org>:
>
> > Hello Jean-Marc,
> >
> > I am not sure how you are calling BaseX from within Eclipse, I remember
> > there are different ways. Normally, I would expect it to simply execute
> > basex, so there shouldn't be any difference. The query optimization should
> > be done in both cases. However, it could be for example that your BaseX
> > integration in eclipse uses XQJ, which could possibly introduce some
> > performance bottlenecks.
> >
> > So if you could shortly describe how you set up BaseX within Eclipse, that
> > would be great.
> >
> > Cheers,
> > Dirk
> >
> > On 09/24/2014 06:33 AM, jean-marc Mercier wrote:
> >> Hi all,
> >>
> >> Happy to write again in this mailing-list, hope you are all doing well
> > guys
> >> !
> >>
> >> I am encountering a small problem running my old xquery modules. I guess
> >> that it is a classical issue, but I can't remember how to look into BaseX
> >> archive :(
> >>
> >> Here is the description of the problem : I am running a query, calling
> >> module_of_mine.xqm, on two different environments.
> >>
> >> The first one is eclipse, linked to the latest interpreter from
> >> BaseX80-20140923.183154 (but I tested also against older interpreter). In
> >> this way, this query saturated my 12 G Java machine after some minutes.
> >>
> >> Then I installed module_of_mine.xqm into BaseX repo, and ran the same
> > query
> >> using basex gui with 4G heap size. The query ran perfectly in some 30
> > sec.
> >>
> >> My first penny guess is that the built-in BaseX xquery profiler is doing
> >> some nice work there ? If so, is there a way to activate / desactivate
> > this
> >> profiler from eclipse or from some configuration files ?
> >>
> >> Cheers,
> >>
> >> Jean-Marc
> >>
> >
> > --
> > Dirk Kirsten, BaseX GmbH, http://basex.org
> > |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz
> > |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer:
> > | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle
> > `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
> >
> >
>
--
Dirk Kirsten, BaseX GmbH, http://basex.org
|-- Firmensitz: Blarerstrasse 56, 78462 Konstanz
|-- Registergericht Freiburg, HRB: 708285, Geschäftsführer:
| Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle
`-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22