[ https://issues.apache.org/jira/browse/HARMONY-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568510#action_12568510
]
Pavel Ozhdikhin commented on HARMONY-5396:
------------------------------------------
4. It would be nice to have results for all options, LOCKED and LOCKED_INSERT is not the only
choice.
5. Egor, I've never told that we should remove TNV_DIVIDED logics. Also, I did not mention
this in my previous comment, I think you should have updated TNV_DIVIDED collector as well,
as soon as you decided to commit new locking options.
Thanks,
Pavel
> [drlvm][em] excess ValueProfiler locking causes degradation on JITted code with profiling
> -----------------------------------------------------------------------------------------
>
> Key: HARMONY-5396
> URL: https://issues.apache.org/jira/browse/HARMONY-5396
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Aleksey Shipilev
> Assignee: Egor Pasko
> Attachments: 0001-ValueProfileCollector-refactoring-to-separate-FirstN-and-Divided-methods.txt,
0002-value-profiling-options-locked-flagged_all-flagged_insert-unsafe.txt, 0002-ValueProfileCollector-implementing-locking-strategies.txt,
0003-value-profiling-options-locked-flagged_all-flagged_insert-unsafe.txt, 0004-value-profiling-reviving-locked-profile.txt,
HARMONY-5396-syncTie.patch
>
>
> During investigation of serious slowdown in some microbenchmark, excess locking in ValueProfiler
was identified.
> Please see Harmony-dev thread for the details: http://markmail.org/message/tatsfbyb7eb3q3rr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|