I've been trying to diagnose some performance issues, I ran the SQL Profiler tool and upon review,I found that all the SQLs are executing within one second.

However, I did find something strange. A event called Audit Logout is taking a very long time. I'm not aware what exactly this does, but it is taking up a lot of CPU time and accounting for large reads.

Audit logout is a security event. It marks when someone disconnects from SQL Server. The time for Audit Logout is the total amount of time the connection existed. So if someone has been connected to your SQL Server for a long time, the number will be quite large. It's not an indication that there is a performance issue.

We are experiencing some very random slowness with one of our stored procedure executions from our web server. We wrote a dummy GUI program that calls our web service method and we're doing a profiler trace to see how long it takes.

We are seeing our stored procedure execution time is about 15 seconds, but the Audit Logout (the ENTIRE connection for that SPID) is 60 seconds. What is going on in that remaining 45 seconds? Is there any way to track what the Audit Logout function is doing?