Conversation
Sequential Navigation Soak A/B✅ HEAD completed the 200-navigation resilience and memory observation. One browser process, one target, and one CDP session navigate CSDN → SegmentFault → Huaban → example.com repeatedly. This run issued 200 Common ancestor Session resilience
A public-page failure is reported separately from an unrecoverable session. The soak requires all navigation attempts, zero failed recovery, zero lifecycle/network ordering violations, and complete resource evidence. Process-tree memory
HEAD memory by 50-navigation quarter
Raw reports and per-navigation boundary samples: workflow run and full Public-site timing and memory are observational. Use the A/B deltas and trend shape as evidence, not as a deterministic performance threshold. |
Spider Bench A/BPublic HEAD: 0 / 0 rows; 0 / 0 sites produced rows; — unexpected empty sites. ✅ Deterministic fixture diagnostic is clean. Common ancestor Public 48-site run · informational
Public-site content, timing, and memory are noisy. This single A/B run reports evidence only; site outcome counts explain missing rows without treating them as a deterministic regression. CPU and memory timelinesThese are bounded 40-point views of the same complete process-tree samples used by the HTML report. CPU uses 100% per occupied logical core; memory lines are RSS first and PSS second when complete PSS samples are available. Basexychart-beta
title "Base CPU"
x-axis "Elapsed seconds" [1.035, 2.538, 3.539, 4.54, 5.041, 6.046, 7.547, 8.551, 10.054, 11.056, 12.058, 13.56, 14.061, 14.562, 16.063, 17.064, 18.566, 19.569, 21.071, 22.072, 23.074, 24.575, 25.575, 27.076, 28.077, 29.079, 29.581, 30.583, 32.085, 33.085, 34.088, 35.593, 36.595, 38.097, 39.099, 40.601, 41.602, 43.104]
y-axis "CPU percent" 0 --> 200
line [63.86, 137.74, 103.9, 167.76, 9.98, 124.96, 113.84, 155.05, 41.91, 125.75, 103.88, 33.94, 2, 5.99, 47.94, 30.01, 3.99, 45.86, 89.9, 27.95, 105.86, 90.03, 107.97, 48.01, 75.91, 133.82, 133.58, 59.9, 57.9, 73.9, 9.98, 81.76, 99.88, 57.88, 37.93, 78.09, 31.96, 139.77]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.035, 1.035, 2.538, 3.539, 4.54, 5.041, 6.046, 7.547, 8.551, 10.054, 11.056, 12.058, 13.56, 14.061, 14.562, 16.063, 17.064, 18.566, 19.569, 21.071, 22.072, 23.074, 24.575, 25.575, 27.076, 28.077, 29.079, 29.581, 30.583, 32.085, 33.085, 34.088, 35.593, 36.595, 38.097, 39.099, 40.601, 41.602, 43.104, 43.896]
y-axis "Memory MiB" 0 --> 500
line [20.91, 112.63, 168.72, 177.08, 224.55, 216.29, 239.38, 216.68, 245.54, 217.63, 241.42, 228.8, 210.16, 199.73, 197.99, 210.63, 208.72, 184.53, 184.77, 211.32, 170.74, 194.75, 222.57, 276.43, 201, 214.05, 279.27, 207.89, 194.85, 195.47, 186.33, 182.99, 229.4, 215.57, 215.36, 213.74, 208.85, 190.92, 247.9, 0]
line [18.92, 110.33, 166.53, 174.79, 222.37, 213.99, 237.04, 214.34, 243.19, 215.51, 239.06, 226.55, 207.8, 197.38, 195.63, 208.26, 206.35, 182.16, 182.41, 208.96, 168.39, 192.41, 220.27, 273.92, 198.64, 212.27, 276.99, 205.53, 192.48, 193.15, 183.96, 180.63, 227.04, 213.21, 213.01, 213.68, 206.5, 188.58, 245.93, 0]
HEADxychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.035, 0.528]
y-axis "Memory MiB" 0 --> 20
line [18.5, 0]
line [16.44, 0]
Deterministic fixture · diagnosticThe fixture exercises 15 routes: 8 are expected to emit rows and 7 intentionally exercise empty, loading, or timeout behavior.
Full HTML, JSON, CSV, logs, and page snapshots: workflow run and full Spider Bench is informational: site failures, missing benchmark reports, failed browser service runs, fixture diagnostics, timing, and performance deltas do not fail the workflow. Build, runner, and artifact infrastructure errors can still fail it. |
Spider Bench A/B✅ All benchmark browser service runs completed; results are informational. Public HEAD: 179 / 240 rows; 37 / 48 sites produced rows; 11 unexpected empty sites. ✅ Deterministic fixture diagnostic is clean. Common ancestor Public 48-site run · informational
Public-site content, timing, and memory are noisy. This single A/B run reports evidence only; site outcome counts explain missing rows without treating them as a deterministic regression. CPU and memory timelinesThese are bounded 40-point views of the same complete process-tree samples used by the HTML report. CPU uses 100% per occupied logical core; memory lines are RSS first and PSS second when complete PSS samples are available. Basexychart-beta
title "Base CPU"
x-axis "Elapsed seconds" [1.035, 2.036, 2.537, 3.038, 3.539, 4.041, 5.042, 6.044, 7.045, 8.045, 9.045, 10.045, 11.046, 12.047, 13.049, 14.051, 15.051, 16.054, 17.054, 18.055, 18.555, 19.557, 20.058, 20.558, 21.56, 22.561, 23.561, 24.562, 25.564, 26.565, 27.566, 28.567, 29.568, 30.569, 31.57, 32.572, 33.574, 34.575]
y-axis "CPU percent" 0 --> 200
line [63.92, 113.86, 121.75, 87.82, 129.74, 149.63, 143.8, 105.68, 163.72, 58.01, 105.97, 114.07, 81.9, 53.95, 91.88, 31.9, 51.95, 35.95, 99.98, 123.85, 123.8, 131.78, 107.91, 131.93, 59.86, 124, 123.94, 15.99, 67.95, 67.92, 23.96, 127.99, 115.85, 2, 0, 149.7, 89.89, 115.88]
xychart-beta
title "Base memory: RSS then PSS"
x-axis "Elapsed seconds" [0.034, 1.035, 2.036, 2.537, 3.038, 3.539, 4.041, 5.042, 6.044, 7.045, 8.045, 9.045, 10.045, 11.046, 12.047, 13.049, 14.051, 15.051, 16.054, 17.054, 18.055, 18.555, 19.557, 20.058, 20.558, 21.56, 22.561, 23.561, 24.562, 25.564, 26.565, 27.566, 28.567, 29.568, 30.569, 31.57, 32.572, 33.574, 34.575, 35.451]
y-axis "Memory MiB" 0 --> 500
line [23.22, 120.08, 152.51, 175.11, 173.57, 201.75, 242.11, 222.27, 218.48, 230.23, 214.58, 241.17, 212.46, 192.9, 212.78, 206.23, 189.04, 184.73, 189.15, 208.73, 219.3, 241.98, 250.69, 264.2, 210.28, 227.04, 261.28, 245.18, 177.04, 191.32, 192.25, 205.4, 259.1, 225.26, 207.98, 221.53, 213.47, 210.66, 239.27, 0]
line [21.17, 117.65, 150.1, 172.69, 171.16, 199.34, 239.76, 219.86, 216.09, 227.83, 212.16, 238.77, 210, 190.45, 210.32, 203.78, 186.6, 182.33, 186.71, 206.28, 216.86, 239.53, 248.24, 261.75, 207.83, 224.58, 258.83, 242.73, 174.58, 188.83, 189.72, 202.9, 256.73, 222.74, 205.46, 219.03, 210.96, 208.15, 236.77, 0]
HEADxychart-beta
title "HEAD CPU"
x-axis "Elapsed seconds" [1.041, 2.043, 3.043, 3.545, 4.045, 4.545, 5.046, 5.547, 6.547, 7.548, 8.549, 10.052, 11.053, 12.054, 13.056, 14.056, 15.056, 16.558, 17.56, 18.561, 19.562, 20.563, 21.564, 23.068, 24.069, 25.07, 26.072, 27.073, 28.075, 29.577, 30.578, 31.579, 32.58, 33.581, 34.583, 36.085, 37.086, 38.087]
y-axis "CPU percent" 0 --> 200
line [49.96, 111.83, 103.94, 115.7, 145.85, 136.06, 133.81, 125.79, 160.06, 63.94, 84, 99.8, 11.98, 29.97, 2, 47.98, 81.97, 59.96, 119.67, 113.89, 133.85, 127.84, 113.92, 55.88, 111.87, 121.81, 15.98, 79.93, 33.91, 93.9, 103.87, 5.99, 0, 0, 61.9, 125.81, 65.94, 117.84]
xychart-beta
title "HEAD memory: RSS then PSS"
x-axis "Elapsed seconds" [0.04, 1.041, 2.043, 3.043, 3.545, 4.045, 4.545, 5.046, 5.547, 6.547, 7.548, 8.549, 10.052, 11.053, 12.054, 13.056, 14.056, 15.056, 16.558, 17.56, 18.561, 19.562, 20.563, 21.564, 23.068, 24.069, 25.07, 26.072, 27.073, 28.075, 29.577, 30.578, 31.579, 32.58, 33.581, 34.583, 36.085, 37.086, 38.087, 38.8]
y-axis "Memory MiB" 0 --> 500
line [20.5, 118.8, 157.58, 192.18, 211.7, 229.22, 254.81, 221.77, 230.21, 256.14, 233.27, 245.92, 225.09, 209.89, 211.22, 170.86, 197.2, 198.47, 179.3, 230.16, 212.46, 222.01, 232.25, 262.2, 206.32, 253.57, 207.98, 191.19, 195.06, 194.34, 267.13, 229.93, 213.9, 211.21, 210.04, 233.49, 228.39, 201.57, 245.93, 0]
line [18.4, 116.41, 155.21, 188.96, 209.3, 226.82, 252.07, 219.25, 227.7, 249.46, 230.75, 243.69, 222.58, 207.38, 208.71, 168.34, 194.81, 195.95, 176.76, 227.62, 209.9, 219.45, 229.71, 259.66, 203.79, 251.04, 205.44, 188.65, 192.53, 191.81, 264.6, 227.39, 211.36, 208.68, 207.5, 230.96, 225.92, 199.11, 243.48, 0]
Deterministic fixture · diagnosticThe fixture exercises 15 routes: 8 are expected to emit rows and 7 intentionally exercise empty, loading, or timeout behavior.
Full HTML, JSON, CSV, logs, and page snapshots: workflow run and full Spider Bench is informational: site failures, missing benchmark reports, failed browser service runs, fixture diagnostics, timing, and performance deltas do not fail the workflow. Build, runner, and artifact infrastructure errors can still fail it. |
1 participant
No description provided.