Subversion Repositories SmartDukaan

Last modification

• Rev 37449 2026-08-28 20:25:12
• Author: amit

• Log message:

  Realme unmerged too: four selenium jobs, one per pool per brand
  
  r37447 merged secondary and tertiary per brand to halve concurrent drivers.
  r37448 reverted that for oppo, because serialising cost it more per imei than a
  second browser did. This reverts it for realme as well, which ends the merge
  experiment entirely.
  
  What the merge actually cost realme is only visible now that oppo is parallel
  again: realme's per-imei went 14.2s -> 29s. It did not change behaviour -- it is
  simply competing with oppo's two browsers for CPU. At 29s its merged ceiling is
  86400/29 = 2,979/day, just under the 3,054/day the daily re-check needs, so no
  batch size could have closed the gap. Two parallel pools restore the ~3,900/day
  it managed historically at four drivers.
  
  Measured before this change (25 min window):
  
  brand needed/day throughput note
  Oppo 8,838 7,661 parallel revert worked, +122%
  Realme 3,054 1,843 merged and CPU-starved
  Vivo 10,082 16,128 surplus, cannot transfer to another brand
  
  Sizes unchanged: oppo 25 per pool, realme 12 per pool, vivo 50+10.
  
  Honest accounting of the merge: it was my idea, sized on per-brand arithmetic that
  ignored contention between brands, and it is now fully reverted. What survives
  from that line of work is the part that actually paid -- reaping orphaned browsers
  (~1.8GB), the per-brand retry caps, and per-brand maxResults. Peak drivers are
  back to 4, which is where they started.
  
  Watch for contention: four browsers is the configuration that produced the 29s
  figure for realme in the first place, so oppo may slow from its current 19.7s.
  Re-measure both before tuning sizes again.