You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some commands, for instance upload, shows the duratoin in the output, for example Created 0 collections and uploaded 1 resources in 292ms.
In the case of execute command, I'm missing this information.
I'm debugging the indexing routine by modifying the indexes and input data. I repeat the same command with different data (collection.xconf, index.xql, input.xml): xst execute "xmldb:reindex('/db/apps/teilex0-publisher/data/playground')" --config admin.xstrc.
Duration of the task is significant for my case.
Alternatives
I run the command using xst and watch the INFO in the eXist-db log.
The text was updated successfully, but these errors were encountered:
I think getting timings on query execution is a useful addition @daliboris
Couple of thoughts on the details:
I prefer to stats similar to what eXide returns
compilation time
execution time
not have the timings include network transport (the overall time that upload reports)
I prefer to have these timings only being output when a flag is set on the command line (e.g. --stats)
For a lot of use-cases, where you want to work with the returned result, additional output would be problematic
and this would break those.
Enhancement
Some commands, for instance
upload
, shows the duratoin in the output, for exampleCreated 0 collections and uploaded 1 resources in 292ms
.In the case of
execute
command, I'm missing this information.I'm debugging the indexing routine by modifying the indexes and input data. I repeat the same command with different data (
collection.xconf
,index.xql
,input.xml
):xst execute "xmldb:reindex('/db/apps/teilex0-publisher/data/playground')" --config admin.xstrc
.Duration of the task is significant for my case.
Alternatives
I run the command using
xst
and watch the INFO in the eXist-db log.The text was updated successfully, but these errors were encountered: