Bug 92224

Summary: [PerfTest] Add performance tests for preload scanning
Product: WebKit Reporter: Kwang Yul Seo <skyul>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abarth, eric, nduca, rniwa, simonjam, tonyg, zoltan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 77037, 90751    

Description Kwang Yul Seo 2012-07-25 00:29:29 PDT
We need performance tests for preload scanning to improve PreloadScanner.
Comment 1 Kwang Yul Seo 2012-07-25 00:37:03 PDT
There was an attempt to improve the performance of preload scanner by running the scanner off-the-main thread. See Bug 63531. 

It seems people used html5-parser benchmark. But I think html5-parser is not suitable to measure the performance of preload scanning because this benchmark is intended to measure the parser throughput.
Comment 2 Kwang Yul Seo 2012-07-26 22:01:11 PDT
Is it possible to delay the loading of elements in perf tests? For example, I'd like to delay dummy.js loading for 1 second to give enough time for the preload scanner to scan the rest of input stream and request preloads.

<script src="dummy.js"></script>...

It seems web-page-replay used for replay performance tests performs a similar function though the delay is recorded, not manually specified.
Comment 3 Eric Seidel (no email) 2013-03-05 02:05:55 PST
I'm not sure how we'd do this?
Comment 4 Adam Barth 2013-03-05 09:40:49 PST
IMHO, we should just use the PLT to measure this sort of thing.  That's really the end-to-end metric that we'd like to move with the preload scanner.