commit | e5fb32b0feee281c69a2795efd7eedc666e49978 | [log] [tgz] |
---|---|---|
author | ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Fri Apr 22 05:41:35 2022 +0000 |
committer | ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Fri Apr 22 05:41:35 2022 +0000 |
tree | 754f721c2e7b178c9c0f5c975261f282089f9f6c | |
parent | ce530c176f04b2c7ced3721a09ee115df66e7419 [diff] |
[JSC] PropertyTable should have compact mode https://bugs.webkit.org/show_bug.cgi?id=239451 Reviewed by Saam Barati. This patch introduces "compact" version of PropertyTable. PropertyTable needs to hold two kind of integers: index and property offset. But for most of objects, both are pretty small and they can fit in uint8_t. If we can use uint8_t for both, we can significantly reduce size of allocated memory for PropertyTable (only 40% of memory is required!). This is good for memory, but also good for performance. Now each CompactPropertyTableEntry is 8bytes while original PropertyMapEntry was 16bytes, so CompactPropertyTableEntry can fit in CPU cache well. Also, not allocating large amount of memory can reduce memory allocation / deallocation cost. One of costly destruction of GC-managed objects is PropertyTable (and CodeBlock), and we can reduce that cost by not allocating much memory. The approach is following. 1. For index vector, we use uint8_t if index can fit within uint8_t. 2. For proprety offset, we use uint8_t and CompactPropertyTableEntry if it is suitable. 3. Once the table gets non-compact, we keep it non-compact since we could have deleted index which has larger than uint8_t. We could improve this strategy when deleted indexes are cleared, but for now, we are taking simple approach. 4. We store isCompactFlag 1 bit in the pointer to the table. 5. We encapsulate functions modifying property table entry in PropertyTable itself, so we do not leak internal compact / non-compact mode to the user of PropertyTable. We remove begin() / end() iterators and instead use forEachproperty, which can implement iteration for each mode more efficiently. We have a further opportunity to improve this further: we can deploy 75% load factor only for compact table. Then we can increase threshold of compact table further and keep more and more tables compact mode. Plus, for small sized tables, small backing memory is better in terms of CPU cache hit (and that's measured in WTF::HashTable, and that's why WTF::Hashtable deploys 75% load factor only for small tables). This is left for the subsequent change. This change is neutral in JetStream2, 0.3% improvement in Speedometer2 with 80% confidence, and 0.41% improvement in RAMification with 95% confidence. * JSTests/stress/change-attribute-structure-transition.js: (shouldBe.JSON.stringify.sd): * Source/JavaScriptCore/bytecode/ObjectAllocationProfileInlines.h: (JSC::ObjectAllocationProfileBase<Derived>::initializeProfile): * Source/JavaScriptCore/dfg/DFGAbstractInterpreterInlines.h: (JSC::DFG::AbstractInterpreter<AbstractStateType>::executeEffects): * Source/JavaScriptCore/dfg/DFGConstantFoldingPhase.cpp: (JSC::DFG::ConstantFoldingPhase::foldConstants): * Source/JavaScriptCore/dfg/DFGOperations.cpp: (JSC::DFG::JSC_DEFINE_JIT_OPERATION): * Source/JavaScriptCore/dfg/DFGSpeculativeJIT.cpp: * Source/JavaScriptCore/ftl/FTLLowerDFGToB3.cpp: (JSC::FTL::DFG::LowerDFGToB3::compileCompareStrictEq): * Source/JavaScriptCore/ftl/FTLOperations.cpp: (JSC::FTL::JSC_DEFINE_JIT_OPERATION): * Source/JavaScriptCore/runtime/ClonedArguments.h: * Source/JavaScriptCore/runtime/IteratorOperations.cpp: (JSC::createIteratorResultObjectStructure): * Source/JavaScriptCore/runtime/JSGlobalObject.cpp: (JSC::JSGlobalObject::init): * Source/JavaScriptCore/runtime/JSGlobalObjectFunctions.cpp: (JSC::JSC_DEFINE_HOST_FUNCTION): * Source/JavaScriptCore/runtime/JSONObject.cpp: (JSC::Stringifier::Holder::appendNextProperty): * Source/JavaScriptCore/runtime/JSObject.cpp: (JSC::JSObject::analyzeHeap): * Source/JavaScriptCore/runtime/JSObject.h: * Source/JavaScriptCore/runtime/ObjectConstructor.h: (JSC::constructEmptyObject): (JSC::createDataPropertyDescriptorObjectStructure): (JSC::createAccessorPropertyDescriptorObjectStructure): * Source/JavaScriptCore/runtime/ObjectConstructorInlines.h: (JSC::objectAssignFast): * Source/JavaScriptCore/runtime/PropertyOffset.h: * Source/JavaScriptCore/runtime/PropertySlot.h: * Source/JavaScriptCore/runtime/PropertyTable.cpp: (JSC::PropertyTable::PropertyTable): (JSC::PropertyTable::finishCreation): (JSC::PropertyTable::visitChildrenImpl): (JSC::PropertyTable::~PropertyTable): (JSC::PropertyTable::seal): (JSC::PropertyTable::freeze): (JSC::PropertyTable::isSealed const): (JSC::PropertyTable::isFrozen const): (JSC::PropertyTable::renumberPropertyOffsets): * Source/JavaScriptCore/runtime/PropertyTable.h: (JSC::isPowerOf2): (JSC::nextPowerOf2): (JSC::PropertyTable::findImpl): (JSC::PropertyTable::find): (JSC::PropertyTable::get): (JSC::PropertyTable::add): (JSC::PropertyTable::remove): (JSC::PropertyTable::take): (JSC::PropertyTable::updateAttributeIfExists): (JSC::PropertyTable::sizeInMemory): (JSC::PropertyTable::reinsert): (JSC::PropertyTable::rehash): (JSC::PropertyTable::skipDeletedEntries): (JSC::PropertyTable::dataSize): (JSC::PropertyTable::canInsert): (JSC::PropertyTable::forEachProperty const): (JSC::PropertyTable::forEachPropertyMutable): (JSC::PropertyTable::begin): Deleted. (JSC::PropertyTable::end): Deleted. (JSC::PropertyTable::begin const): Deleted. (JSC::PropertyTable::end const): Deleted. (JSC::PropertyTable::table): Deleted. (JSC::PropertyTable::table const): Deleted. * Source/JavaScriptCore/runtime/RegExpMatchesArray.h: * Source/JavaScriptCore/runtime/Structure.cpp: (JSC::Structure::dumpStatistics): (JSC::Structure::Structure): (JSC::Structure::materializePropertyTable): (JSC::Structure::nonPropertyTransitionSlow): (JSC::Structure::isSealed): (JSC::Structure::isFrozen): (JSC::Structure::flattenDictionaryStructure): (JSC::PropertyTableStatisticsExitLogger::~PropertyTableStatisticsExitLogger): (JSC::Structure::getConcurrently): (JSC::Structure::getPropertiesConcurrently): (JSC::Structure::getPropertyNamesFromStructure): (JSC::Structure::toStructureShape): (JSC::Structure::dump const): * Source/JavaScriptCore/runtime/Structure.h: (JSC::CompactPropertyTableEntry::CompactPropertyTableEntry): (JSC::CompactPropertyTableEntry::key const): (JSC::CompactPropertyTableEntry::setKey): (JSC::CompactPropertyTableEntry::offset const): (JSC::CompactPropertyTableEntry::setOffset): (JSC::CompactPropertyTableEntry::attributes const): (JSC::CompactPropertyTableEntry::setAttributes): (JSC::PropertyTableEntry::PropertyTableEntry): (JSC::PropertyTableEntry::key const): (JSC::PropertyTableEntry::setKey): (JSC::PropertyTableEntry::offset const): (JSC::PropertyTableEntry::setOffset): (JSC::PropertyTableEntry::attributes const): (JSC::PropertyTableEntry::setAttributes): (JSC::PropertyMapEntry::PropertyMapEntry): Deleted. * Source/JavaScriptCore/runtime/StructureInlines.h: (JSC::Structure::get): (JSC::Structure::forEachPropertyConcurrently): (JSC::Structure::forEachProperty): (JSC::Structure::add): (JSC::Structure::remove): (JSC::Structure::attributeChange): Canonical link: https://commits.webkit.org/249881@main git-svn-id: http://svn.webkit.org/repository/webkit/trunk@293210 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git@github.com:WebKit/WebKit.git WebKit
or
git clone https://github.com/WebKit/WebKit.git WebKit
If you want to be able to track Subversion revision from your git checkout, you can run the following command to do so:
Tools/Scripts/git-webkit setup-git-svn
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
iOS, tvOS and watchOS are all considered embedded builds. The first time after you install a new Xcode, you will need to run:
sudo Tools/Scripts/configure-xcode-for-embedded-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for embedded simulators:
Tools/Scripts/build-webkit --debug --<platform>-simulator
or embedded devices:
Tools/Scripts/build-webkit --debug --<platform>-device
where platform
is ios
, tvos
or watchos
.
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.