Graphit - Trace

[F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN]

Fabric 6.5.9

I'm trying to profile the execution of a graphit using the trace command. Already tried with level=debug, operations=graphit, even category=solutions, but got no entry related to the graphit start, iterations, end, etc. What is necessary to make it to work properly? Be aware that we added other operations/categories also (e.g. webservice, sqlcommands, etc.). Please advise. Thanks.

[ltyR937rLurXtsgj5KWa6A4bWhUE9JxjxLZO38A]

how did you run you graphit file(direct in studio/BW/WS) ?

my tests result : attached trace file: example.fabrictrace.txt

command that i run : trace SESSION_SCOPE test3 'categories=commands;operations=graphit;';

i run it using BW

[F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN]

how did you run you graphit file(direct in studio/BW/WS) ?

my tests result : attached trace file: example.fabrictrace.txt

command that i run : trace SESSION_SCOPE test3 'categories=commands;operations=graphit;';

i run it using BW

Hi @Rwedkabha, hope you are doing well.

Graphit is being triggered from the webservice Java function.

In the file that you shared, I don't see any line that indicates the graphit operation.

I see only connection, preparedStatement and sqlCommand that are all database related.

Of course that Graphit includes many queries within, but I want to see its details, similar to what Broadway profiler provides.

Some testing was done and running a set of queries from Graphit is taking 350ms, while running these queries, one-by-one, on Fabric console, when summing up their times, are taking less than 100ms.

Cheers.

[157aq9Ud3GJlkIVikTS1SzhhiP3x1Vrj0jAjZ3X]

He ran Graphit to get these results. What similar example you have from trace, where you see different results from the trace system. Can you share such trace output?

[F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN]

When trying, I see similar output, but nothing specific to the graphit execution as a whole, like when it started, when it ended, no line with operation graphit.

As I commented before, Some testing was done and running a set of queries from Graphit is taking 350ms, while running these queries, one-by-one, on Fabric console, when summing up their times, are taking less than 100ms., I would like to figure out why it takes so long when run by Graphit. I can only assume that it has some bootstrapping and termination process that consumes a lot of time.