note jthalhammer <p>Perl::Critic has been through several rounds of optimizations, so I doubt you'll be able to squeeze much more performance out of it (but patches are always welcome).</p> <p>Most of the time is spent within PPI, parsing the file. So running a client/server arrangement won't help much. However, installing [cpan://PPI::XS] will give you a small speedup.</p> <p>Tuning your policy set might help some. Certain polices like like RequireTidyCode are considerably more intensive than others. Also, any policy that has 'PPI::Document' or 'PPI::Token::Word' in the applies_to method tends to be slower than other policies that have a more narrow focus. So if you can disable those policies (or just run them less often), then you might get a little better results.</p> <p>Editors like Komodo run Perl::Critic in the background as you edit the file, so you don't notice the performance as much. Perhaps you could get vim to do the same?</p> <p>Never mind folks that tell you when to save your files or how often to critique or syntax-check your code. Everyone has a different workflow. Do whatever works best for you.</p> <div class="pmsig"><div class="pmsig-458049"> <p> Jeffrey Thalhammer<br/> <a href="http://www.imaginative-software.com">Imaginative Software Systems</a><br/> </p> </div></div> 949688 949688