On Fri, Oct 29, 2021 at 6:10 AM Skip Montanaro
wrote:
> 1. I use numpy arrays filled with random values, and the output array is
> also a numpy array. The vector multiplication is done in a simple for loop
> in my vecmul() function.
>
probably doesn't make a difference for this exercise, but num
Skip> 1. I use numpy arrays filled with random values, and the output array
is also a numpy array. The vector multiplication is done in a simple for
loop in my vecmul() function.
CHB> probably doesn't make a difference for this exercise, but numpy arrays
make lousy replacements for a regular list
Remember that py stone is a terrible benchmark. It only exercises a few
byte codes and a modern CPU’s caching and branch prediction make minced
meat of those. Sam wrote a whole new register-based VM so perhaps that
exercises different byte codes.
On Sun, Oct 31, 2021 at 05:19 Skip Montanaro
wrote
One use case which seems significant to me but I don’t think has been
explicitly mentioned is annotations using a package with stubs where the
stubbed typing API is slightly different than the runtime API.
For example sometimes additional tape aliases are defined for convenience in
stubs without
> Remember that py stone is a terrible benchmark.
I understand that. I was only using it as a spot check. I was surprised at
how much slower my (threaded or unthreaded) matrix multiply was on nogil vs
3.9+. I went into it thinking I would see an improvement. The Performance
section of Sam's design
I’ve just published the September steering council update, also included
below:
https://github.com/python/steering-council/blob/main/updates/2021-09-steering-council-update.md
Just as a reminder, if you have any questions or concerns, feel free to
contact us or open an issue in the SC repo:
https
