Closed
Bug 495640
Opened 16 years ago
Closed 16 years ago
Lots of range requests are generated when seeking
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
DUPLICATE
of bug 501031
People
(Reporter: sylvain.pasche, Unassigned)
Details
Seeking in a video that isn't loaded yet generates lots of Range requests and can be slow.
For instance,
1. Load http://www.double.co.nz/video_test/transformers480.ogg and click play
2. Seek to 50% (before the video is in cache).
I watched the HTTP requests with the ngrep tool:
ngrep '[^-]Range: b' -W byline -d eth0 host double.co.nz > log
The following range requests are issued when seeking:
grep "Range:" log
Range: bytes=13856768-.
Range: bytes=6930432-.
Range: bytes=6283264-.
Range: bytes=6606848-.
Range: bytes=6553600-.
Range: bytes=6541312-.
Range: bytes=6537216-.
Range: bytes=6533120-.
Range: bytes=6529024-.
Range: bytes=6524928-.
Range: bytes=6520832-.
Range: bytes=6516736-.
Range: bytes=6512640-.
Range: bytes=6508544-.
Range: bytes=6504448-.
Range: bytes=6496256-.
Range: bytes=6488064-.
Range: bytes=6483968-.
Range: bytes=6549504-.
That's 20 requests around the middle of the file (of length 13858902 bytes).
I guess that optimizing the number of range requests could reduce seeking time and be more gentle with the Web server.
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•