[
https://issues.apache.org/jira/browse/HUDI-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922544#comment-16922544
]
Davis Eric Broda commented on HUDI-234:
---------------------------------------
I don't know enough about different JVMs to say whether different factors would
be worthwhile in the long term, but in the short term getting a single factor
that works woudl be preferable, followed by updates later if it proves to be
either too large or too small on other JVMs.
As to how to determine the factor, probably get a group of sample objects and
write an instrumentation implementation in a test environment. In a simpler
test environment, with objects selected so that they are easier to run through
instrumentation it should be easier to get numbers returned. See what the
maximum difference is between the two, and then add a bit more for safety. That
should give us a good starting value, to be updated if further issues arise.
> Graceful degradation of ObjectSizeCalculator for non hotspot jvms
> -----------------------------------------------------------------
>
> Key: HUDI-234
> URL: https://issues.apache.org/jira/browse/HUDI-234
> Project: Apache Hudi (incubating)
> Issue Type: Bug
> Components: Write Client
> Affects Versions: 0.5.0
> Reporter: Vinoth Chandar
> Priority: Major
>
> https://github.com/apache/incubator-hudi/issues/860 bug report
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
