[Speed] performance 0.5.5 and perf 1.3 released

[Antoine Pitrou]

On Mon, 29 May 2017 22:29:44 +0200
Victor Stinner <victor.stinner at gmail.com>
wrote:
> 
> > This is quite common in network and/or distributed programming where you
> > want to allow logging many events for diagnosis of unexpected runtime
> > issues (because many unexpected conditions can appear), but with
> > those logs disabled by default for performance and readability reasons.  
> 
> Note: I would suggest to use a preprocessor or something like to
> *remove* the calls if performance is critical. It is the solution was
> chose in a previous company working on embedded devices :-)

Then you lose the ability to enable debug logs on user /
customer systems.  Unless the preprocessor is run each time the user
changes the logging configuration, which adds another layer of
fragility.

> But I'm not sure that it's really doable. I don't think that it's
> matter so much to provide backward compatibility. It's very easy to
> get an old version of performance if you want to compare a new version
> with old results.

I don't know.  It means that benchmark results published on the Web
are generally not comparable with each other unless they happen to be
generated with the exact same version.  It reduces the usefulness of
the benchmarks suite quite a bit IMHO.

Let's ask the question a different way: was there any necessity to
update those dependencies?  If yes, then fair enough.  Otherwise, the
compatibility breakage is gratuitous.

Regards

Antoine.