Received: by 10.50.185.202 with SMTP id fe10mr1402992igc.3.1326967301712;
        Thu, 19 Jan 2012 02:01:41 -0800 (PST)
X-BeenThere: shedskin-discuss@googlegroups.com
Received: by 10.231.68.202 with SMTP id w10ls19985698ibi.7.gmail; Thu, 19 Jan
 2012 02:01:41 -0800 (PST)
Received: by 10.50.185.202 with SMTP id fe10mr1402974igc.3.1326967301150;
        Thu, 19 Jan 2012 02:01:41 -0800 (PST)
Received: by 10.50.185.202 with SMTP id fe10mr1402973igc.3.1326967301139;
        Thu, 19 Jan 2012 02:01:41 -0800 (PST)
Return-Path: <drr...@gmail.com>
Received: from mail-tul01m020-f181.google.com (mail-tul01m020-f181.google.com [209.85.214.181])
        by gmr-mx.google.com with ESMTPS id wm10si8274372igc.1.2012.01.19.02.01.41
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 19 Jan 2012 02:01:41 -0800 (PST)
Received-SPF: pass (google.com: domain of drr...@gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of drr...@gmail.com designates 209.85.214.181 as permitted sender) smtp.mail=drr...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-tul01m020-f181.google.com with SMTP id up10so9500724obb.40
        for <shedskin-discuss@googlegroups.com>; Thu, 19 Jan 2012 02:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=bbXH2d5azHB8ZduwiFnbRbm1AS8BT8hIuXdU4oVFPTQ=;
        b=S28RKDfHZK0ZG/Dkzw7YKb61KnkzhmU6vFdPbkGxjus2pM1uafGRWEv7kb+k/RVgu9
         qrQ0wh6PXzQ0rGEmXmeXSzPsPeDC6TLQ+mWgSwKEfNMtFNCN1lGOhw8hTLkHFqmi6iYh
         Iy79org5Lr4XhS0s+TdQcXpLodInCq5r7nGtw=
MIME-Version: 1.0
Received: by 10.182.160.1 with SMTP id xg1mr22401060obb.30.1326967300961; Thu,
 19 Jan 2012 02:01:40 -0800 (PST)
Received: by 10.182.70.197 with HTTP; Thu, 19 Jan 2012 02:01:40 -0800 (PST)
In-Reply-To: <CAFHc1QYd-zVnmsGLhg_H9w_CU=riGrBc9HjkAZOHAOxyzh+8mA@mail.gmail.com>
References: <5ea7f706-ec71-4fd9-9bb8-4d44e37b8...@e8g2000yqd.googlegroups.com>
	<CAFHc1QZDdUeT_ZHCtpAUGm9X9B9Bri=NkVw-kdsYStwQ=C5...@mail.gmail.com>
	<CA+m65S2dqZAT=1fUEvUJ0kcQLaaS2D3joNqYoWke60+JRho...@mail.gmail.com>
	<CAFHc1QYd-zVnmsGLhg_H9w_CU=riGrBc9HjkAZOHAOxyzh+...@mail.gmail.com>
Date: Thu, 19 Jan 2012 10:01:40 +0000
Message-ID: <CAFHc1QbJj7L719ogdbcBsXCfO7QMTvveEZRXYkPv58D8bf=...@mail.gmail.com>
Subject: Re: osnews article
From: Raphael Clifford <drr...@gmail.com>
To: shedskin-discuss@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> The pattern matching test seems to finish almost instantly with no
> output so I omitted it. =A0If anyone knows it should be run I would be
> happy to run it.
>
>

I got the pattern matching benchmarks to run.

First using

([a-zA-Z][a-zA-Z0-9]*)://([^ /]+)(/?[^ ]*)|([^ @]+)@([^ @]+)

pypy : timing 8s, memory 91072maxresident
shedskin : 39s, memory 7680maxresident

Now using

([a-zA-Z][a-zA-Z0-9]*)://([^ /]+)(/?[^ ]*)

pypy : timing 4.5s, ,memory 76640maxresident
shedskin : timing 3s, memory 7664maxresident

Now some notes and comments.

First, you will notice that in fact I rounded to the nearest second in
my first email, not the nearest half second as I claimed.  Second, the
memory usage figures in linux are hard to interpret due to the way the
operating system works.  The first answer
http://stackoverflow.com/questions/131303/linux-how-to-measure-actual-memor=
y-usage-of-an-application-or-process
briefly sets out the main reasons why the simplest number you get
isn't necessarily what you want and the rest of the post tells you
ways to get better measurements.  Lastly, you will see that shedskin
is very very variable in its timings.  I will leave the devs to
discuss why this is :)

Raphael