That's strange, I've never seen such excessive CPU usage of talk. If I were you, I'd mail || advise both users to stop using the talk utility for a while, have them enter "mesg n" to disallow write access and see if it drops down. Probably yes. Then ask then what exactly they have done during this "chat session", for example, pasting large buffer of code / lines may slow down the daemon.