spamd caching configuration

[Ronan]

does spamd read all sitewide config files in /etc/mail/spamassassin when 
it starts and keeps them in memory so that whenever a spamc connects to 
it its there for quicker / more efficenet processing...?

im asking becuase i cant run the full rules and suribls on my primary 
mailhub because it keeps giving me a

 spam acl condition: spamd connection to 127.0.0.1, port 783 failed: 
Connection timed out

i presume this is due to the cpu not being able to handle all the 
connections simultaneously...

SA is implemented through the exim acl connecting to spamd which is started
/usr/local/bin/spamd -d -r /logs/spamd.pid
because of this i am thinking i may need to migrate all spam scanning to 
a dedicated server and have all 3 hubs point to it.
has anyone else had this sort of problem...

--
Regards
Ronan McGlue
==============
Analyst/Programmer
Information Services
Queens University Belfast
BT7 1NN