view release on metacpan or  search on metacpan

ramblings/yapceu2015.html  view on Meta::CPAN

# Characteristics

##Before

    Resident Size (perl 5.6)_____9756

    Resident Size (perlcc 5.6)___9072  (7%)

##After

    Resident Size (perl 5.14)____18704

    Resident Size (perlcc 5.14)__12091 (35%)
---
# Why 35% better?

Aggressive string optimizations with -O3, from dynamic to static.

---
# Why 35% better?

Aggressive string optimizations with -O3, from dynamic to static.

The compiler is also now 2-3x faster than the old compiler. The
build process was reduced from 2 hrs to 40 minutes.
---
# Why 35% better?

Aggressive string optimizations with -O3, from dynamic to static.

But the problem is more why 90% worse with 5.14

---
# Development

First compiler version 1.42 (Feb 2012) with 5.14 could compile and run
all cPanel code. 3 months work after moving to Texas.

Worked on several optimizations and 5.18 support until 2014,
when cPanel was ready to switch over. Still 5.14 (and 5.18 in test).

1.44 (Feb 2014) added the full core testsuite, and passes it.
Before we had ~20 fails.

Problems:
  - global destruction (please use lexicals)
  - attribute handlers
  - compile-time perlio layers

---
# Development

Until 1.52, the final version Sep 2014, we fixed:

- global destruction (rewrite)
- Dynaloader/XSLoader handling
- tons of corner cases detected in the testsuite
  (added mro, utf8, re tests), and with modules
- ~5 CPAN module fixes

esp. DBI, Encode, Net::DNS, IO::Socket::SSL, DBD::mysql for
compile-time stored pointers, being restored at run-time, boom!

---
# Beware

Still the old golden rule for the compiler:

**BEGIN for compile-time, INIT for run-time initializations.**

Esp. do not compile pointers into your shared library, initialize them
at **INIT**.
---
# Testing

The core testsuite runs now all tests in *12:40min* fully parallel.
With ccache *~5min*.

Before it needed *16min* for 75% of it.

---
# Testing

The core testsuite runs now all tests in *12:40min* fully parallel.
With ccache *~5min*.

Before it needed *16min* for 75% of it.

* our uncompiled perl 5.22 variant needs *8m40m*,
* a p5p perl 5.23 needs *11-13min*,
* 5.14 *15-19min*

---
# Broken

Moose, Coro, FCGI, v5.22

We'll rather fix perl 5.22 and B::C first, and make the Moose bloat history.
I maintain in p2/potion a perl6 like MOP in ~40 lines, which is 200x faster.

Fixing Moose is not priority, fixing perl5 is.
Coro next, when we'll start using it.

---
# Development

Via perl11 in nearby Austin we formulated goals
for perl6 feature integration.

* types (YAPC::EU 2012 Riga talk)
* B::CC optimizations (YAPC::EU 2013 Kiev talk, ~6x faster)
* p2/potion development (YAPC 2014 talks, ~5-200x faster)
* rperl (restrict the syntax, map to static C++ types, ~7-350x faster)
* plan on shared modules, less memory, better arrays and hashes
  and types (=> no magic, static optims and dispatch) and much more.

---
# Next goal

We skipped all versions from 5.16 to 5.20, since they got worse
in almost all aspects: memory, security, compiler API.