UncommonTrapBlob

Performance Tuning
#1

Does anyone know what ‘UncommonTrapBlob’ is? ???
I’m profiling and it keeps showing up in the -Xprof output and apparently it’s taking up 4.3% of execution time.


     Compiled + native   Method                        
  4.4%   296  +     0    net.movegaga.jemu2.FrameWork.updateTexture
  4.3%     2  +   285    UncommonTrapBlob
  3.8%   254  +     0    jef.video.GfxManager.decode
  3.7%   246  +     0    jef.cpu.Z80.exec
  0.9%    61  +     0    jef.sound.chip.AY8910.AY8910Update
  0.8%    52  +     0    jef.video.BitMapImpl.toBitMap
...
...
#2

An UncommonTrapBlob happens when the compiler decides that it the compilation its working on, just isn’t gonna happen. Things like optimizatins that are taking too long, are prime candidates for an Uncommon Trap. What command like flags are you running with?

#3

Thanks for your reply :slight_smile:
I’m running on the client, with no flags except -Xprof.

EDIT: Correction, I was running on the server. It doesn’t happen on the client.

#4

There really isn’t much you can do I suppose… maybe refactor your code?

#5

I also checked the old non-lwjgl version running in an applet, and that one doesn’t have the UncommonTrapBlob. So the additions I did probably cause it but there’s not much refactoring I can do there. Just one simple class was added.
Anyway, thanks for the explanation.