On 11/13/19 5:52 AM, Victor Stinner wrote:
Le mer. 13 nov. 2019 à 14:28, Larry Hastings a écrit :
I did exactly that in the Gilectomy prototype. Pulling it out of TLS was too
slow,
What do you mean? Getting tstate from a TLS was a performance
bottleneck by itself? Reading a TLS variable see
Thanks for the encouragement!
I've been working some more on it since I had some more free cycles in the last
few days and I think I've got to the limit of my capabilities. I think I've got
it to a point where it needs more eyes because my experience level writing code
in the python interprete
Thanks Thomas. If there are any questions, I'm happy to do my best to
answer those too.
On Wed, Nov 13, 2019 at 3:39 AM Thomas Wouters wrote:
>
> Perhaps this should've been announced a little more widely: we have
> upcoming Steering Council elections, and nominations close soon -- end of
> day
I wouldn't worry too much about the the Singletons in this issue; they could be
solved in any of several ways, all of which would be improvements conceptually
-- if performance and backwards compatibility were resolved.
In theory, the incr/decr pair should be delegated to the memory store, with
Petr, Eric: sure, my question is only about the internal C functions.
I have no plan to change the existing C API.
Le mer. 13 nov. 2019 à 14:52, Eric V. Smith a écrit :
> The last time we discussed this, there was pushback due to performance
> concerns. I don't recall if that was actually measure
Le mer. 13 nov. 2019 à 14:28, Larry Hastings a écrit :
> I did exactly that in the Gilectomy prototype. Pulling it out of TLS was too
> slow,
What do you mean? Getting tstate from a TLS was a performance
bottleneck by itself? Reading a TLS variable seems to be quite
efficient.
Mark Shannon wro
On 11/12/2019 5:03 PM, Victor Stinner wrote:
Hi,
Are you ok to modify internal C functions to pass explicitly tstate?
The last time we discussed this, there was pushback due to performance
concerns. I don't recall if that was actually measured, or just a vague
unease.
I've long advocated (
On 11/12/19 2:03 PM, Victor Stinner wrote:
Hi,
Are you ok to modify internal C functions to pass explicitly tstate?
I did exactly that in the Gilectomy prototype. Pulling it out of TLS
was too slow, and storing it in a global wouldn't work with multiple
actually-concurrent threads.
//ar
On 2019-11-12 23:03, Victor Stinner wrote:
Hi,
Are you ok to modify internal C functions to pass explicitly tstate?
In short, yes, but:
- don't make things slower :)
- don't break the public API or the stable ABI
I'm a fan of explicitly passing state everywhere, rather than keeping it
in "g
Perhaps this should've been announced a little more widely: we have
upcoming Steering Council elections, and nominations close soon -- end of
day *this Friday*. Five seats need to be filled. (We have four nominations
so far, but I have no idea how many people are gearing up to nominate in
the next
10 matches
Mail list logo