David Chord wrote in a message to All:
 DC> Hello All!
 DC> Ok, a question for those who run packet sort.
 DC> I'm considering using it here *if* it's going to work OK 
 DC> in/after 2k (or be updated between now and then).
Is there any indication of y2k problems w/ this?
 DC> However, I'd like to know if it'll be worth it.
It's easy enough to set up,  and for a comparison you can always rem stuff 
out.
 DC> I run a hub system with a number of points and downlinks, many 
 DC> of whom generally only send 1 or 2 messages at a time instead.
I have it invoked on incoming largish bundles,  and not for incoming netmail 
or smaller outgoing bundles.  It's all in how you set up your batch files.
 DC> 2-3 times I get compressed packets of over 100Kb from a couple 
 DC> of my uplninks (generally 1 large packet each (largest 
 DC> averaging 600Kb, the other averaging around 200Kb, then little 
 DC> bits during the day), and several smaller (30-40+) lots of <20 
 DC> messages (usually <10). Also note that a lot of these packets 
 DC> contain messages for one echo (probably around 60-70% of the 
 DC> time I recieve 1-10 messages for one echo only) 
 DC> I run a 486dx2-50, 8Mb ram (inc cache), Squish/386 under 
 DC> DesqView (spawned for mail processing) and a 2Mb cache.
I run this stuff under DV here too.  What are you using for a cache,  BTW?  
The above-mentioned differences in processing I handle with semaphores,  and 
short batch files to set 'em.
 DC> Would packetsort do anymore than just toss messages in the 
 DC> correct order? 
It doesn't change the order of stuff,  in terms of putting the areas it 
encounters in alphabetical order or anything like that,  it just puts stuff 
for any given area all together,  as far as I know (I have a -q on my batch 
file line that invokes squish,  so I don't usually watch it).
It *does* speed things up quite a bit,  though.
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------