From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Python-on-guile
Date: Sat, 24 Apr 2021 16:41:39 +0200 [thread overview]
Message-ID: <CAGua6m20-XXDyoYvo7V8iXPn33chFTzjG=+DzRCXpESvRTOX7w@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m2+1su5Nxw=wZexvkkgFkKXnN1aK_6ZaVF1W22OK6JXnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]
To note is that 'continue' is killing performance for python-on-guile
programs, so by changing the
code to not use continue lead to python-on-guile running twice the speed of
python3. The reason is that
the while loop is used as
(while (...)
(let/ec continue
...))
And the let/ec is probably not optimally compiled. Python-on-guile will
check the loop for continue usage and if not then it will skip the let/ec.
I attached the code not using continue
On Sat, Apr 24, 2021 at 2:59 PM Stefan Israelsson Tampe <
stefan.itampe@gmail.com> wrote:
> Actually changing in (language python compile),
>
> (define (letec f)
> (let/ec x (f x))))
>
> To
>
> (define-syntax-rule (letec f)
> (let/ec x (f x))))
>
> Actually lead to similar speeds as python3.
>
>
>
> On Sat, Apr 24, 2021 at 1:26 PM Stefan Israelsson Tampe <
> stefan.itampe@gmail.com> wrote:
>
>> Pro tip, when running this on guile the scheme code that it compilse to
>> is located in log.txt.
>> If you ,opt the resulting code in a guile session you might be able to
>> pinpoint issues that
>> delays the code execution.
>>
>> On Sat, Apr 24, 2021 at 12:04 PM Mikael Djurfeldt <mikael@djurfeldt.com>
>> wrote:
>>
>>> (I should perhaps add that my script doesn't benchmark the object system
>>> but rather loops, conditionals and integer arithmetic.)
>>>
>>> Den fre 23 apr. 2021 17:00Mikael Djurfeldt <mikael@djurfeldt.com> skrev:
>>>
>>>> Hi,
>>>>
>>>> Yesterday, Andy committed new code to the compiler, some of which
>>>> concerned skipping some arity checking.
>>>>
>>>> Also, Stefan meanwhile committed something called "reworked object
>>>> system" to his python-on-guile.
>>>>
>>>> Sorry for coming with unspecific information (don't have time to track
>>>> down the details) but I noticed that my benchmark script written in Python,
>>>> and which computes the 20:th Ramanujan number, now runs 60% faster than
>>>> before these changes.
>>>>
>>>> This means that python-on-guile running on guile3 master executes
>>>> python code only 2.6 times slower than the CPython python3 interpreter
>>>> itself. :-)
>>>>
>>>> Have a nice weekend all,
>>>> Mikael
>>>>
>>>>
[-- Attachment #2: ram.py --]
[-- Type: text/x-python, Size: 1778 bytes --]
# ramanujan.py -- Compute the N:th Ramanujan number
#
# Copyright (C) 2018-2021 Mikael Djurfeldt
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
# Version 2
# return the N:th Ramanujan number (sum of two cubes in more than one way)
#
def ramanujan (n):
w = 0 # Ramanujan number candidate
b0 = 1 # first second term to try
while n > 0:
w += 1 # try next candidate
# increase initial b0 until 1 + b0^3 >=w
while 1 + b0 * b0 * b0 < w:
b0 += 1
a = 1
a3 = 1
b = b0
b3 = b0 * b0 * b0
count = 0 # number of ways to write w
while a <= b:
s = a3 + b3
if s < w:
a += 1 # if sum is too small, increase a
a3 = a * a * a
elif s == w:
count += 1 # found a sum!
if count > 1:
n -= 1
break
b -= 1 # increase b both if sum too large and to find next way to write w
b3 = b * b * b
else:
b -= 1
b3 = b * b * b
return w
print (ramanujan (21))
next prev parent reply other threads:[~2021-04-24 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 15:00 Python-on-guile Mikael Djurfeldt
2021-04-23 20:41 ` Python-on-guile Linus Björnstam
2021-04-24 10:04 ` Python-on-guile Mikael Djurfeldt
2021-04-24 11:26 ` Python-on-guile Stefan Israelsson Tampe
2021-04-24 12:59 ` Python-on-guile Stefan Israelsson Tampe
2021-04-24 14:41 ` Stefan Israelsson Tampe [this message]
2021-04-24 15:19 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 8:20 ` Python-on-guile Mikael Djurfeldt
2021-04-25 10:21 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 8:46 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 10:54 ` Python-on-guile Dr. Arne Babenhauserheide
2021-04-25 11:54 ` Python-on-guile Vivien Kraus via General Guile related discussions
2021-04-25 10:18 ` Python-on-guile Stefan Israelsson Tampe
2021-04-27 12:29 ` Python-on-guile Nala Ginrut
-- strict thread matches above, loose matches on Subject: below --
2022-02-19 19:36 python-on-guile Stefan Israelsson Tampe
2019-06-14 18:06 python-on-guile Stefan Israelsson Tampe
2019-06-22 21:07 ` python-on-guile Arne Babenhauserheide
2019-06-26 18:45 ` python-on-guile Nala Ginrut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGua6m20-XXDyoYvo7V8iXPn33chFTzjG=+DzRCXpESvRTOX7w@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mikael@djurfeldt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).