AM> Well this could have something to do with it!  2Mb cache...  16Mb ram I

 AM> assume...  8.5mS... 



Yeah, well, this could contribute to it slightly!



 PM>> I also sort the inbound packets into area + subject + date

 PM>> + time order. Having them in area order seems to speed up

 PM>> Squish, although I loose some time sorting the packets.



 AM> Does Squish do this sorting, or is it something you do?



I do this with a separate program and feed the resulting packet into
Squish. Since I read my messages straight off the message base, I wanted
them sorted into subject and date order. I made it sort by area because it
didn't add much overhead and I thought it would speed up Squish. If you're
using an OLR then you probably don't care what order the messages come in.



 PM>> There are two choices for deleting old records. You can set

 PM>> a maximum number of messages (as you have) and Squish will

 PM>> delete anything over that limit when it tosses. Obviously

 PM>> this can slow it down quite a lot. I've got no idea how

 PM>> much difference it makes if it doesn't have to delete any

 PM>> records during tossing.



 AM> I recently upped the limit on a few of the echos at their limits, and

 AM> gained not much at all - which is strange, because originally, it was

 AM> twice as fast as current when the echos weren't full, up to 25msg/sec.



Have you tried running SQPACK against it. Packing the message base may
help, and it can't hurt!



 PM>> The other approach (the one I use) is to set the maximum number of

 PM>> days to keep. In this case Squish just tosses the message without

 PM>> checking to see if any messages should be deleted.



 AM> Trouble is some echos like OS/2 come in in big lumps and could overflow

 AM> the 5200 mark quite easily before Sqpack gets to run, no?



If you keep a lot of messages then yes, you could easily overflow the
limit. The biggest echo I've got hovers around 1,000-1,500 messages, so
it's pretty unlikely I'm going to toss an extra 4,000 message in one go.



 PM>> If you use the second approach, then you have to run SQPACK

 PM>> to delete all the old records. It also packs the database

 PM>> to remove the unused space. I usually run it every couple

 PM>> of days, but you can run it as often as you like. On a

 PM>> large message base it could take a while though.



 AM> If Squish can delete old messages when it hits the set limit (4000 say),

 AM> then why can't it automatically delete old messages by date in the same

 AM> way without having to run Sqpack afterwards?



 dunno. Possibly because figuring out what to delete based on
the date requires too much work during tossing.



 PM>> There's a parameter in the Squish configuration file called

 PM>> 'buffers'. If you haven't already, make it 'buffers large'

 PM>> and see if it helps.



 AM> Already done from day one. :(



In that case you're on your own. You could always collect the Squish echo
and see if anyone has some more ideas. If you find anything, let me know.
I'd like to see if I can break the 100 msgs/sec mark :-)



 AM> BTW, the clips from your logs had Squish terminating with about 2Mb

 AM> free - why do you have 2Mb free and I have 512Kb free?



Beats me. Could be something to do with the amount of memory I've got or
maybe that my message bases are a lot smaller.





Paul



--- GoldED/2 2.42.G1114