Bug 17145 - Add some #ifdef'd AtomicString counters for judging String efficiency
Summary: Add some #ifdef'd AtomicString counters for judging String efficiency
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-01 16:37 PST by Eric Seidel (no email)
Modified: 2008-02-01 19:55 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2008-02-01 16:37:31 PST
Add some #ifdef'd AtomicString counters for judging String efficiency

I've been meaning to do this for some time.  We should have an #ifdef mode where StringImpl constructors always do an AtomicString hash lookup to see if an atomic version of that impl already exists.  We could then collect statistics and see how many duplicates of what strings are held in memory.

Likewise, if we kept track, we could see what AtomicStrings are never (or rarely) used and possibly not load them into the AtomicString hash on startup.

Finding unused atomic strings is likely not very interesting, since all the ones used in code are very very small.  However, finding strings which really should be Atomic *is* very interesting.