SCM

[#1007005] Implement profiling

View Trackers | Feature Requests | Download .csv | Monitor

Date:
2007-06-25 13:34
Priority:
3
State:
Open
Submitted by:
Andrus Moor (kobruleht)
Assigned to:
Nobody (None)
Category:
Group:
Resolution:
None
 
Summary:
Implement profiling

Detailed description
npgsqlconnection() should have option to log all commands sent to server and their durations to text file.

NpgsqlEventLog.Level = LogLevel.Debug works but slows down program too much.
Also this result file has too many unnessecary information.

MS SQL net data provider has profiling capabilities.

npgsql should also have profiling capabilites in client side.

Followup

Message
Date: 2008-12-21 02:04
Sender: Jon Hanna

I'm not entirely sure what you mean here. I didn't know the MS provider had profiling, I've always used the profiler that comes with the server itself, can you point to the documentation?

I've sometimes used a class that logs everything that goes through the stream, so attached is a patch that makes it a bit (but only a bit) more user-friendly. It does log every byte raw though, so probably more detail than many would want (very useful when working on Npgsql itself, but I can't see users finding this much detail very useful, especially since one could get the same info from a TCP tracer).

Attached Files:

Attachments:
Logging.patch

Changes:

Field Old Value Date By
File Added365: Logging.patch2008-12-21 02:04talliesin
Powered By FusionForge