Steps

1. Edit ALFRESCO_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/core-services-context.xml

Find the indexThreadPoolExecutor bean and then change the corePoolSize property value from 10 to 0

2. Edit ALFRESCO_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/subsystems/fileServers/default/file-servers-context.xml

Find the fileServerConfiguration bean and then add the following property :-

<property name=”coreServerConfigBean”>
<bean>
<property name=”threadPoolInit”>
<value>4</value>
</property>
</bean>
</property>

3. Edit ALFRESCO_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/scheduled-jobs-context.xml

Find the schedulerFactory bean and then add the following property :-

<property name=”taskExecutor”>
<bean>
<property name=”threadCount”>
<value>1</value>
</property>
</bean>
</property>

4. Edit ALFRESCO_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/domain/quartz.properties

Comment out the org.quartz.threadPool.threadPriority property setting

h2. Result

Before: Server startup in 90625 ms, 66 threads. 267.2mb
After: Server startup in 87435 ms, 27 threads. 259.1mb

Ok, this is not really a great result in terms of improving startup time or memory consumption…  but I learnt quite a lot along the way about the Alfresco system, and how closely it is coupled with Spring .