![]() ![]() ![]() Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) T H R E A D -Ĭurrent thread (0x00a0f718): VMThread # Java VM: Java HotSpot(TM) Client VM (1.4.2_13-b06 mixed mode) # An unexpected error has been detected by HotSpot Virtual Machine: do you see any risks / conflicts in running JPDA and YK (JVMPI) at the same time?Ĭode: Select all = I know IDEA does this, but wanted to hear your thoughts/ do you think it running an application in production with profiling enabled is appropriate? would this introduce stability issues? if there's no overhead / risk in running with YK during production too, it seems like a no brainier that all users should be doing so as one nnever knows when a snapshot may be useful. does running in profile mode affect hotspot optimizations? can you briefly explain why you feel that the overhead is virtually zero? in other words what is YK doing or not doing to not impact performance when profiling? can you quantify "virtually zero" with a number like 5% ? The YK documentation states that the overhead of using JVMPI (w/ JDK 1.4) is virtually zero when measuring is not performed. I downloaded and tried the same with YK 7 and things work great! I'm really excited as I've been trying to do this for a while now. Holy cow, it does work with the YK 7 b2020 EAP!! I had tried starting the application with JPDA and profiling options with YK 6 and the application would start up fine however when I tried to connect using a remote debugger, I would get a connection refused message. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |