Hi Jean-Marc,
However I can't find the log left by fn:trace, or prof:time. Do you know
where these traces append in this configuration ?
The dump/trace output can be viewed when turning on the query info
(-V). As the output is generated by the server, it will first be
collected and then sent
Christian,
Hello.
I was trying to profile code through a client / server as you advised. Thus
I installed the module into the basex repository, and launched it through a
client.
However I can't find the log left by fn:trace, or prof:time. Do you know
where these traces append in this
Hi Jean-Marc,
Currently no. You can use the prof:current-ns()
I thought about this one, but isn't this method less accurate than prof:time
If your measurements don’t fall below milliseconds, it should make no
difference.
Benchmarking is a complex field on its own, however:
• In BaseX, it’s
Hi Christian,
Thx for your answer.
it is advisable to remove all trace() calls from the code before doing
performance comparisons.
You're right. From another side, the trace functions are called very few
times (68 calls), compared to the time execution (about two minutes to run
the entire
Hello Christian,
I have some small questions over the profile module.
1) The following code
declare function local:sequence($nb){for $i in 1 to xs:integer($nb) return
$i};
prof:time(fn:count(local:sequence(100)))
return 4.94 ms.
It means that you lazy evaluate the query {for $i
5 matches
Mail list logo
