Impact of an Asynchronous Mirror / Full Recovery Model on Performance For an asynchronous mirror in SQL Server 2008 R2, using the full recovery model is required. 

Assuming that the network and disk IO on both sides of the Mirror can keep up with the transaction logs and mirroring, are there still performance penalties for this over not having a mirror and having the database in simple recovery? If so, what kinds of operations are effected and what causes them to be effected?
With an async mirror there should be little to no performance impact on the active system.  When you are in full recovery there is more transaction log activity on the system than if the database was in simple recovery mode, but that's about it.  Are you seeing specific waits or something that prompted the question?