PersiaML/PERSIA

PS needs to be evicted by business policy

nealgavin opened this issue · 1 comments

  1. feature score
    Each feature has a feature _ score that is calculated a
    feature_score=clk_coeffpos_ins_num+nonclk_coeffneg_ins_num
    On push, feature _ score is always accumulated
  2. time_decay
    End _ day (sample time) will trigger time _ decay
    Time _ decay, the feature _ score is attenuated by CVM _ plugin.decay _ ratio
  3. shrink_table
    After time _ decay, or when feature _ num exceeds Max _ features during training, shrink _ table is triggered
    If one of the conditions is met, it is deleted:
    ● score < _delete_threshold
    ● value.unseen_days > _delete_after_unseen_days
    ● _ select _ prob _ slot _ set.get (value.slot) = = 1 & & score < _ select _ delete _ threshold/Id Group Id type feature, increase delete threshold
    ● _ photoid _ slot _ set.get (value.slot) = = 1 & & value.unseen _ days > 2/Delete after two days of combined photo _ ID feature
    If feature _ num is still greater than Max _ features after deletion, it will be deleted from small to large according to feature score until feature _ num < Max _ features is satisfied
stale commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.