Okay, so it appears it's not likely to gain much anymore for C-libraries because the interpreter lock is being released where possible already, allowing it to run on separate cores at that point. What if the 'C-library' is another instance of Pike? Could it be (made) possible to have Pike release it's interpreter locks if it would be known to not have any inter-Pike processing there anyway?
Say, there is a function implemented in Pike which could be very CPU-intensive and only handles locally created variables. I can imagine some definition which would tell Pike which variables are interfacing between the two instances, after which instance #1 and instance #2 do their own separate processing (and interpreter locking) without interfering with the other instance until it has data to return (if any).
Regards,
Arjan
__________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________