Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excess trace logging in FbCommand [DNET467] #458

Closed
firebird-automations opened this issue Nov 9, 2012 · 4 comments
Closed

Excess trace logging in FbCommand [DNET467] #458

firebird-automations opened this issue Nov 9, 2012 · 4 comments

Comments

@firebird-automations
Copy link

Submitted by: Yurij (yurij)

Relate to DNET622

IsDebug property is removed from FbConnection in version 3.0 and replaced with TRACE directive conditional. This solution has two problems:

1) LogCommand method in FbCommand is active (TRACE was defined when building 3.0 version) and debug output is flooded with messages from it, reducing overall performance.

2) It is impossible to control trace output in production with "is debug" flag, as in previous versions.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Author

Commented by: Baldur Fürchau (bfuerchau)

Actual in Version 4.7.0.0 a trace-option should be added!
I have tested with a modification of the source to stop the traceoutput.
This give me an improvement of up to 70% to 90%, because the building of the tracestring takes to much time!
To stop the trace like discussed in the blog does not improve pervormance and is not an Option for Performance.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue relate to DNET622 [ DNET622 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants