09-25-2012, 05:16 PM
(09-24-2012, 09:41 PM)hyakki Wrote: log and profiler from r2736 attached maybe it can help discover new information on the boss loading screens (gpu usage is low on this scene)The best would be to "Reset the Profiler Information" just before the start of the loading screen and quit Jpcsp just after it. This would capture profiler information just for this slow loading sequence.
From the profiler info you provided, it seems that only a few methods are used intensively:
Code:
_S1_2_88F8DD0 847,509,440 instructions (15.357%), 103,335 calls (088F8DD0 - 088F8E8C, length 48)
_S1_2_8A062F0 788,938,191 instructions (14.296%), 275,949 calls (08A062F0 - 08A06754, length 282)
_S1_2_88CD178 510,032,684 instructions (9.242%), 8,098 calls (088CD178 - 088CF584, length 2308)
_S1_2_88F87F8 482,409,533 instructions (8.742%), 69 calls (088F87F8 - 088F89D4, length 120)
From a first analysis, _S1_2_88F8DD0 looks like a simple Bubble Sort algorithm and could be implemented into native Java.
Thanks!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log