Using AutoCL and /combatlog never caused any problems, even combat logs at around 50 MB never caused a drop in WoW's performance. The size was a problem for Windows' Editor though, so I started using Textpad: www.textpad.com
Is there any efficient way to filter out the healing Prayer of Mending did with WWS? I'm curious as to how much that adds up, but couldn't come up with anything other then searching + adding up the whole combat log, but that's not exactly something I wanna do after each raid.
Btw, had a talk with a buddy ingame. He said combatlog range could no longer be changed, while I was pretty sure this was still possible. Anyone who has the lowdown on what range is possible with logging? I've never cared much about parses, but thinking it could be fun to try out.
BTW, one thing I noticed people haven't stated yet it seems is that the combat log range will no longer be settable in 2.1.
Its really annoying and I didn't even realize at first on the PTR but your combat log files individually are pretty worthless. So, you will need to get multiple people to log the combat and use them with WWS (it will auto merge them).
This is all the aftereffect of a really bad hack to fix people being able to see combat log messages in arena during prep time (instead of actually fixing the real server code so you can't see the messages during that time).
This will also have the result of breaking a lot of boss mods that weren't syncing.
EDIT: may as well be current since I re-happened across this post. This change did not go through.
This thread probably belongs on the UI Interface forum. But in the way of a response:
SW_Unilog has the potential to be the best for tracking this as long as many people are using sw_stats for damage meters already. The information sorting could use a few tweaks but there is a lot in there.