[NEMO-154] Handle skewness information in SchedulingConstraint

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.2
• Labels: compiler runtime
• Assignee: Jeongyoon Eo
• Reporter: Jeongyoon Eo
• Created: 10/Jul/18 06:56
• Updated: 07/Mar/20 06:51
• Resolved: 18/Feb/19 12:12

Description

Currently, skewness is encoded as boolean isSkewed value of HashRange, which is set in DataSkewRuntimePass. This results in KeyRange implementation tied with an arbitrary feature('skewness').

 

After IR-based dynamic optimization is done, we need to refactor this to let DataSkewRuntimePass toss the skewness information needed for scheduling to SchedulingConstraint, in IR-level.

Issue Links

• is blocked by: NEMO-60 IR-based dynamic optimization