performance for Replication and trigger

Hi guys,
I have issue related transaction replication and trigger. In my company, we
have transaction replication and then there are some triggers in the tables
in subscriber server. When the data replicated into table, then fired the
trigger. Recently, it causes performance issue when data become bigger.
Somebody told me that microsoft doesn't recommand to use replication and
trigger together. Is that true? How can I work around? Thanks.
You can define the trigger with the NOT FOR REPLICATION attribute to prevent
it firing on synchronization.
HTH,
Paul Ibison