I try the following insert query:
insert node <coverage id=''>....</coverage> into /server[@endpoint='anEndpointId']/formal/lastimage/harvested/coverages
We run BaseX782. The database has a lot of namespaces in general but none of them is outside the scope of coverage element. As you can see we use the full path in the insertion.

In general, get queries are fast, the only problem we have is with insertions and replacements.

Regards
Yannis

On 05/16/2014 12:40 PM, Lukas Kircher wrote:
Hi Yannis,

we need a little bit more information - as Dirk already pointed out.

It would be especially interesting to know what you mean with ‘record’. Are you
trying to insert an element or a document? The internal process differs greatly
for both operations.

Which version of BaseX are you using? What about Namespaces in the database?

Cheers,
Lukas


On 16 May 2014, at 11:35, Dirk Kirsten <dk@basex.org> wrote:


Hello Yannis,

that is hard to tell. Please describe in more detail what you do, which
commands/queries you run and possibly input data.

For sure it is not in a general case - I just tested it on a 112MB XMark
file and a update of one node took around 200ms. But depending on what
you do it might be normal (e.g. if you search the node with an
exponential runtime it might very well be).

Cheers,
Dirk

On 16/05/14 11:26, Ioannis Kavvouras wrote:

Hello,

We try to insert/replace a record (size of ~500KB) in a file of 100MB.
The query requires more than 10minutes in order to completed.
Could you please tell if the previous is normal?

Regards
Yannis

-- 
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