Here are some hints and tips that can help you use SQL Server Profiler more effectively.
If a queue is pausing too often, this may mean that the priority of the thread is too low. To boost thread priority, assign a lower percentage to the Boost Priority field in the From Server dialog box. You should also increase the Reduce Priority field in the From Server dialog box. For more information, see Advanced Options.
If a computer running Microsoft® SQL Server™ is running too slowly, SQL Server Profiler may have too many traces or a complex trace may be running. Stop any running traces to see if performance improves. If stopping traces improves performance, then examine your traces carefully to make sure they are not tracing more information than necessary. Make sure you are not running too many complex traces simultaneously.
Large trace files can use significant amounts of disk space and can be slow and expensive to send across networks. Reduce the size of a saved trace file by removing unwanted event types and/or data columns and applying filters to limit the trace to a specific trace event criteria, such as Connection ID, SPID, or a set of values for Application Name. Save the trace file with the same name or a new name.
Warning Saving a trace file with the same name overwrites the original file, causing any of the originally captured events or data columns that were removed or filtered to be lost