https://bugzilla.wikimedia.org/show_bug.cgi?id=67168
Bug ID: 67168
Summary: Investigate effect of multiple release branches on
HHVM's JIT system
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: Deployment systems
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Web browser: ---
Mobile Platform: ---
Tim described it better than anyone else:
HHVM has a mode called RepoAuthoritative, which requires you to
pre-compile all the bytecode before you run the program. It's said to
give 30% faster execution or so. During pre-compilation for
RepoAuthoritative, an attribute called AttrUnique is set on functions
and classes that have only one implementation for a given name.
So when there is only one MW version in pre-compilation, AttrUnique
should be set on most things, but if there is more than version, it
should be set on almost nothing. If you don't use RepoAuthoritative,
it should also be set on nothing. AttrUnique is used by the IR and MC
emitters, apparently for optimisation.
My suspicion is that having multiple versions of MW will not
completely stop code from being JITed, rather it will just give you a
slowdown of up to 30%, equivalent to not using RepoAuthoritative.
I think a good benchmark would be to parse some large page that has
anything Lua-related stripped out of it (since LuaSandbox still has
bugs in it). Then get benchmarks with:
* RepoAuthoritative off
* RepoAuthoritative on with one MW version precompiled
* RepoAuthoritative on with two MW versions precompiled
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
