Bug 143490 – optimize content extension interpreting

• Component: WebCore Misc.
• Status: RESOLVED FIXED

[Alex Christensen]

There are some simple optimizations that make things a lot faster:
  Not interpreting data urls.  These can be many kilobytes of base64 encoded things like images.
  When jumping to the DFA root, don't re-add all the actions.  We handle the actions from the root in special optimized ways, anyway.

[Alex Christensen]

Created attachment 250280 [details]
Patch

[Alex Christensen]

Created attachment 250281 [details]
Patch

[Alex Christensen]

http://trac.webkit.org/changeset/182492

[Benjamin Poulain]

View in context: https://bugs.webkit.org/attachment.cgi?id=250281&action=review

> Source/WebCore/contentextensions/ContentExtensionsBackend.cpp:80
> +    if (resourceLoadInfo.resourceURL.protocolIsData()
> +        || resourceLoadInfo.resourceURL.protocolIsJavaScript())

This could be on a single line.

> Source/WebCore/contentextensions/ContentExtensionsBackend.cpp:130
> +    WTFLogAlways("Time added: %f microseconds %s", (addedTimeEnd - addedTimeStart) * 1.0e6, resourceLoadInfo.resourceURL.string().utf8().data());

Isn't that a bit too verbose? Maybe printing the average after every 100 urls would be easier to work with?

> Source/WebCore/contentextensions/DFABytecodeCompiler.cpp:113
> +    // If we jump to the root, we don't want to re-add its actions to a HashSet.
> +    // We know we have already added them because the root is always compiled first and we always start interpreting at the beginning.

That's a good point!

[Alex Christensen]

Touching URL.h broke things.  Undid that in http://trac.webkit.org/changeset/182500