Closed
Bug 1345703
Opened 7 years ago
Closed 7 years ago
[meta] Byte stream-specialized tokenizer
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 1351107
| Performance Impact | low |
People
(Reporter: shu, Assigned: Waldo)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
A tokenizer specialized for Latin1 should be a healthy speed up for Latin1 scripts.
|
Reporter | |
Updated•7 years ago
|
Summary: [meta] Latin1-specialized tokenizer → [meta] Byte stream-specialized tokenizer
|
|
Reporter | |
Comment 1•7 years ago
|
||
See comments in bug 1344152. UTF-8 seems to be the better approach. Being able to parse byte streams directly without inflating is likely the the important thing, regardless of approach.
|
||
Updated•7 years ago
|
Whiteboard: [qf]
|
||
Comment 2•7 years ago
|
||
Marking p1 because parsing improvements directly lead to load time improvements. Inflation is both linear on the source, and also the output is twice the size, causing lots of memory/cache churn.
Whiteboard: [qf] → [qf:p1]
|
|
||
Updated•7 years ago
|
Whiteboard: [qf:p1] → [qf:p2]
|
|
||
Comment 3•7 years ago
|
||
Jeff can you evaluate if this work still makes sense?
Assignee: nobody → jwalden+bmo
Flags: needinfo?(jwalden+bmo)
Whiteboard: [qf:p2] → [qf:p1]
|
|
||
Updated•7 years ago
|
Whiteboard: [qf:p1] → [qf:p3]
|
Assignee | |
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jwalden+bmo)
Resolution: --- → DUPLICATE
|
||
Updated•2 years ago
|
Performance Impact: --- → P3
Whiteboard: [qf:p3]
You need to log in
before you can comment on or make changes to this bug.
Description
•