Performance optimizations: object pooling, StringBuilder caching, and message caching #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reduces object allocations and GC pressure during CSS parsing through targeted caching and pooling strategies. Expected ~40% reduction in allocations and ~25-30% improvement in parse speed for large CSS files.
Changes
Object Pooling
LocatorPoolwith ThreadLocal pools (max 32 per thread) to reuse Locator objectsLocator.createLocator()to acquire from pool instead of allocatingLocator.clear()method for pooling supportStringBuilder Caching
AbstractCSSParseraddEscapes()to use cached StringBuildergetCachedStringBuilder()/returnCachedStringBuilder()for future useMessage Caching
ConcurrentHashMap(soft limit 100 entries)getParserMessage()Utility Optimizations
ParserUtils.trimBy(String, int, int)with bounds checking to avoid defensive copiesParserUtils.equalsIgnoreCase(CharSequence, CharSequence)for allocation-free comparisonPerformance Monitoring
PerformanceMetricsclass (enable with-Dhtmlunit.cssparser.metrics=true)Example Usage
Thread Safety
All caching uses ThreadLocal (StringBuilder, LocatorPool) or ConcurrentHashMap (message cache) to avoid synchronization overhead.
Testing
LocatorPoolTestfor pooling behavior and thread isolationPerformanceTestfor benchmarking and validationParserUtilsTestfor new utility methodsWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
checkstyle.org/opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/tools/linux64/java/bin/java /opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/tools/linux64/java/bin/java -jar /opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/xml/tools/xml-extractor.jar --fileList=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/working/files-to-index16585075317241321623.list --sourceArchiveDir=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/src --outputDir=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/trap/java(dns block)commons.apache.org/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/htmlunit-cssparser/htmlunit-cssparser org.codehaus.plexus.classworlds.launcher.Launcher clean verify -q(dns block)junit.org/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/htmlunit-cssparser/htmlunit-cssparser org.codehaus.plexus.classworlds.launcher.Launcher clean verify -q(dns block)www.puppycrawl.com/opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/tools/linux64/java/bin/java /opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/tools/linux64/java/bin/java -jar /opt/hostedtoolcache/CodeQL/2.23.8/x64/codeql/xml/tools/xml-extractor.jar --fileList=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/working/files-to-index16585075317241321623.list --sourceArchiveDir=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/src --outputDir=/home/REDACTED/work/htmlunit-cssparser/.codeql-scratch/dbs/java/trap/java(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
Performance Optimizations for CSS Parser
Problem
The CSS parser, while functionally correct, has several performance bottlenecks that impact parsing speed, especially for large CSS files:
Performance Impact:
Solution
Implement targeted performance optimizations that:
Implementation Plan
1. String Builder Pooling
Problem:
StringBuilderobjects are created and discarded frequently.Solution: Use ThreadLocal StringBuilder cache
Usage in parser:
2. Locator Object Pooling
Problem: Locator objects are created for every token but are short-lived.
Solution: Implement a simple object pool
Update LocatorImpl to support pooling: