Subversion Repositories SmartDukaan

Last modification

• Rev 37447 2026-08-27 20:36:36
• Author: amit

• Log message:

  Selenium: one browser per brand instead of one per pool
  
  Oppo and Realme each ran secondary and tertiary as separate @Scheduled jobs, so
  each brand opened two ChromeDrivers at once and the fleet ran four. Each driver
  tree costs roughly 850MB. This box co-hosts a 9.4GB tomcat with ~3GB available
  and has been OOM-killed twice this month -- tomcat was the victim both times, so
  peak concurrency is the thing that matters here.
  
  Combined into one job per brand. Nothing downstream changes: the two pools differ
  only in which named query fills them, and both already funnel into the same
  updateActivationDate -> checkWarranty -> saveActivation path. They are disjoint by
  construction (secondary excludes anything with a FofoLineItem, tertiary is
  FofoLineItem-based); distinct() is insurance, not a fix for a known overlap.
  
  Sizing matters, because merging SERIALISES work that used to run in parallel and
  keeping the old batch sizes would quietly cost throughput. Measured post-cap at
  10.2s/imei (oppo, down from 14.6 after r37445) and 14.2s/imei (realme), solving
  M * 86400 / (300 + M*t):
  
  oppo 2 parallel jobs x10 = 4,299/day -> merged 15+15 = 4,277/day (parity)
  realme 2 parallel jobs x10 = 3,910/day -> merged 10+10 = 2,959/day (-24%)
  
  Oppo is sized to hold parity because it is already short of its 4,798/day need.
  Realme is left at 20 -- it needs 2,243/day, so it can absorb the dip in exchange
  for shorter batches and a shorter-lived browser.
  
  What this saves and does not save: total driver-SECONDS are roughly unchanged,
  which is the point of resizing. PEAK concurrent drivers halves from 4 to 2.
  
  Also skips starting a browser at all when both pools come back empty -- currently
  never true, but it costs nothing and a browser launched to do nothing is pure
  waste on this box.
  
  checkOppoImeiStatus/Tertiary and the realme equivalents are left in place for
  manual invocation; they are simply no longer scheduled.