Hi christian,
Hope your holidays went finely !
I can send you the XQUERY files, that consists mainly the graph database V0.0 open sourced files. However, you won't be able to reproduce the issue without a database sample. Actually, I can't send you my database, that has been built with my client data, thus containing confidential informations.
Don't you have another idea to go ahead with this issue ? If not, I'll have to build a database from public data, like a wikipedia dump, but it will take some time.
Cheers
2014-10-06 13:53 GMT+02:00 Christian Grün christian.gruen@gmail.com:
Hi Jean-Marc,
back again. Could you possibly send us the problematic query files (provided that these can be run without too much initialization overhead)?
Cheers, Christian
On Sat, Sep 27, 2014 at 11:34 AM, jean-marc Mercier jeanmarc.mercier@gmail.com wrote:
Dirk,
Hello ! Sorry, the problem seems to be on BaseX side.
1- I have tried to use eclipse IDE setting the interpreter as a client. Doesn't work, it saturated my Java machine. 2- I have tried to sollicitate directly the BaseX client module through client:connect and client:query. Doesn't work, it saturated my Java
machine.
3- Then I toggled totally the eclipse IDE : I opened a local server
instance
basexserver.bat, I opened a dos windows basexclient.bat, and tried to RUN the query file directly on the client console. Doesn't work, it still saturated my JAVA Machine. 4- I finally tested that the same query ran perfectly using the BaseX
Gui.
My first penny guess is that this problem could be linked to this closed bug, that we encountered some 7 months ago :
https://github.com/BaseXdb/basex/commit/5a926e0ea74b3e4a09f9a735ef7f19006413...
. This impression is motivated because I have the same symptoms than for this bug : as I terminate the query, the eclipse console IDE freeze and I have to kill the BAseX server process to retrieve.
5- Thus I tried also to force non verbose mode using Basex client interpreter (setting -v options). Doesn't work, it still saturated my
JAVA
Machine.
Do we have any way to check if a query run in verbose mode ?
Cheeres,
Jean-Marc
2014-09-26 16:20 GMT+02:00 jean-marc Mercier <jeanmarc.mercier@gmail.com :
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