[ https://issues.apache.org/jira/browse/FELIX-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall resolved FELIX-939. ----------------------------------- Resolution: Fixed Fix Version/s: fileinstall-0.9.2 Assignee: Richard S. Hall Committed patch to address this, please close. I also deployed a snapshot, so it would be a good idea for people to start playing with it to make sure we didn't introduce any issues. > Optimize File Install > --------------------- > > Key: FELIX-939 > URL: https://issues.apache.org/jira/browse/FELIX-939 > Project: Felix > Issue Type: Improvement > Environment: generic > Reporter: Sahoo > Assignee: Richard S. Hall > Fix For: fileinstall-0.9.2 > > Attachments: FELIX-937-938-939.patch, FELIX-937-938-939.patch.v2, > FELIX-937-938-939.patch.v3 > > > File Install has a dedicated thread for every directory. That thread wakes up > periodically and then does the following: > 1. Iterates over all the bundles by calling context.getBundles > 2. Finds out all bundles which belong to watchedDir. It starts them. > 3. Finds if there is any new jar file in the watchedDir. It installs them. > 4. Finds out if any jar has been deleted from watcheDir. It uninstalls > corresponding bundles. > 5. Finds out if any jar has been modified. It updates the corresponding > bundles. > I think there is some scope for optimization here. Especially step #2 seems > redundant if there has been change in the file system. More over, if out of > all the bundles in the system, only a few belong to watchedDir, then the > current implementation performs poorly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.