Very poor performance of JNI AttachCurrentThread on Linux (original) (raw)
Dmitry Samersoff dmitry.samersoff at oracle.com
Thu Mar 28 12:05:57 PDT 2013
- Previous message: Very poor performance of JNI AttachCurrentThread on Linux
- Next message: Very poor performance of JNI AttachCurrentThread on Linux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Adam,
Thank you!
-Dmitry
On 2013-03-28 23:02, Adam Domurad wrote:
On 03/11/2013 01:19 PM, Dmitry Samersoff wrote:
Adam,
Sorry! I can't provide any estimations right now. But it's a high priority issue in my queue, and I plan to provide a fix as soon as it become possible. -Dmitry On 2013-03-06 21:45, Adam Domurad wrote: On 03/01/2013 11:00 AM, Dmitry Samersoff wrote: Adam,
Thank you for advice! I'm looking for a possibility to remove getstackbounds function entirely as Dean suggested. But it takes some time. Hi again, not to be a bother, but do you have a rough time-frame that the fix will take? Thanks, -Adam As per our off-list chat, I have attached my implementation of a revised implementation of getstackbounds with a small test-case. As far as performance is concerned, it's an order of magnitude faster from my timings. This should be suitable given that no problems were reported with the old implementation. Happy hacking, -Adam
-- Dmitry Samersoff Oracle Java development team, Saint Petersburg, Russia
- Give Rabbit time, and he'll always get the answer
- Previous message: Very poor performance of JNI AttachCurrentThread on Linux
- Next message: Very poor performance of JNI AttachCurrentThread on Linux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]