[
https://issues.apache.org/jira/browse/OPENJPA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476502
]
John Stecher commented on OPENJPA-160:
--------------------------------------
Craig 1) We are using the CPU sampling feature of the profiler to not slow the
runtime down to much. Its basically sampling the processor every n
microseconds and seeing whats active on the processor when the sample occurs.
I have found this shows a pretty good representation of wall clock time for the
runtime. 2) and 3) I think Patrick has answered and I look forward to testing
the patch. 4) I am open to trying clone as it would show a non-synchronized
mechanism for setting up the new object versus the possibly synchronzied
newInstance call. Looking at the code we should be able to make clone work in
this case. I know from performance testing I did a long time back in the J2EE
1.2 days that clone was something like 4x faster than actually calling
newInstance but it was a nightmare to get the clone to actually work in most
cases and setup the object correctly.
I look forward to the new patch Patrick.
> Reuse BrokerImpl objects
> ------------------------
>
> Key: OPENJPA-160
> URL: https://issues.apache.org/jira/browse/OPENJPA-160
> Project: OpenJPA
> Issue Type: Sub-task
> Reporter: Michael Dick
> Assigned To: Patrick Linskey
> Attachments: newprofile.jpg, openjpa-160-patch.txt,
> openjpa-160-patch.txt, openjpa-160-patch.txt, openjpa-160-patch.txt,
> perf2.jpg, perf3.jpg, profile_explicitclass.jpg
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
