# from Ken Williams via RT
# on Monday 24 January 2011 19:25:
Show quoted text>When I did a Devel::NYTProf profile just now, 93.4% of the time of
> compat.t was spent in CORE::system().
IIRC, it runs the full "perl Makefile.PL; make; make test" on many
different scenarios, so almost everything is going to profile as
CORE::system() - you would need to profile one level lower to find the
bottleneck, which I'm guessing is overhead of directory setup and
teardown for each scenario, including recreating the Build.PL,
makefile, module files, etc.
I looked at breaking this into smaller tests which could be
parallelized, but never got it done after some refactors to the test
libs. Also, compat.t is somewhat futile as a developer test, since
good coverage of this actually requires multiple systems and
configurations, so it would be much better to remove it from t/ and
instead have a CI process keeping an eye out for breakage.
--Eric