Single CPU core fully utilized with Trace session [CORE5203] #5484
Submitted by: Thomas Steinmaurer (tsteinmaurer)
I'm basically seeking for assistance pin-pointing an issue here with
Unfortunately, it is only reproducible in FB TraceManager at the moment.
When starting a trace session with e.g. the following configuration:
database = employee
and triggering a few monitoring table queries behind the scene in a
I guess not very helpful, but this is the stack trace of the high CPU
I'm afraid, not very helpful. :-(
What else could I provide so that you can investigate the offending
I'm aware, this all is vague and I would prefer a simple isql based test
The text was updated successfully, but these errors were encountered:
Commented by: @AlexPeshkoff
Thomas, as a temporal workaround I recommend use of isc_info_svc_to_eof when reading service data.
BTW, it's more efficient in general (using bigger network packets) therefore recommended when service can produce a lot of data. Our utilities fbsvcmgr & fbtracemgr are using it to access trace data.