Gray sampling data in Purepaths

I've had occurences where most of the time of a Purepath is not accounted for, even though the top level entry point is correctly specified. I was hoping to find a hint in the gray data (resulting from sampling if I'm not mistaken?) but even when showing "All Nodes", I don't get any hint. I just get "time holes" in the Purepath.

Has that happened to anyone? Any suggestion?

PS : Sorry for posting these two topics here if this is the wrong place, I just thought this was the least irrelevant section to post them in.

Regards,

Dorian

hi Dorian,

could you attach such a PurePath and tell us a little more about your environment?
maybe we'll get a better idea of the behavior you see, then.

best,
Christian 

just from this part of the PurePath it's hard to tell.
I guess you can't export/share a PurePath here? you could remove the confidential strings during export.

I would definitely look at the place where this sync HTTP call is done (client side), which is not visible on this screenshot.
I can't really tell you more right now. 

Christian

Uploading the exported Purepath.pp_missingTime.dts

I'm trying to understand how the 28 seconds could possibly belong to getInputStream() as suggested by this Purepath, i.e AFTER the exception occurs but BEFORE getInputStream() finishes.

I hardly see how

weblogic.net.http.SOAPHttpURLConnection.getInputStream() could account for this time itself.

Any idea how I could investigate this further?

And while we're at it, if you have any clue as to why there is more time belonging to "Database Summary" under getSchadenliste() (388652.38 ms) than the entire duration of the Purepath (134899.75 ms), I'm also interested.

The JDBC Client used here is single threaded, so there's no way this could be the summed elapse of a bunch of parallel SQL queries.