[
https://issues.apache.org/jira/browse/HUDI-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922624#comment-16922624
]
Vinoth Chandar commented on HUDI-234:
-------------------------------------
First of all, this is a solid and very interesting. So thanks everyone :) for
contributing
>>If they aren't that different, then maybe we could just take the value a
>>given object would have in HotSpot JVM, and multiply by some safety factor
>>(1.5? or 2?) to get something a bit larger.
Good point. But the object sizes could vary dynamically right? We may not be
able to get baseline hotspot values on a non-hotspot JVM even if we figure out
the safety factors? For e.g; the HoodieRecord object can have avro payload and
its size could vary based on schema, compression code etc..
Let me take a stab at how we use the estimation across the code and see if
there is a simpler alternative .. cc [~nishith29] who wrote most of this code.
> 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)
