[
http://jira.jboss.com/jira/browse/JBVFS-26?page=all ]
Ales Justin resolved JBVFS-26.
------------------------------
Resolution: Done
PathTokenizer has been rewritten to be more optimized.
Other methods - findChild, structureFind, ... - should benefit from that.
Optimize frequently called methods to improve AS boot time.
-----------------------------------------------------------
Key: JBVFS-26
URL:
http://jira.jboss.com/jira/browse/JBVFS-26
Project: JBoss VFS
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.Beta11
Reporter: Dimitris Andreadis
Assigned To: Ales Justin
Priority: Critical
Fix For: 2.0.0.Beta12
Attachments: as5_vfs_hot_spots.tar.gz, jboss-5.0.0.Beta4.zip,
jboss-5.0.0.CR1-rev73546.zip
Profiler analysis of AS bootstrap in JBAS-5224 shows a lot of time is spent in VFS
methods.
Look in particular at:
http://jira.jboss.com/jira/secure/attachment/12320206/as5_hotspots_20_may...
One direction is to try to reduce the number of calls to the VFS methods from the
callers, so this needs to be handled elsewhere.
But another goal is to improve the execution time of the hotspot methods in vfs, e.g.
PathTokenizer.getTokens are called about +330k times in beta4 and ~600k times in trunk.
AbstractVirtualFileHandler.structuredFindChild has the same increase in calls as
PathTokenizer.getTokens.
AbstractVirtualFileHandler.checkClosed have increased from ~1.4million calls to 3million
calls
MatcherStrategy.subtypeOf have increased from 500k to 680k calls.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira