HR>> run=f:\os2\cache.exe /LAZY:9 /MAXAGE:12500 /DISKIDLE:7500
HR>> /BUFFERIDLE:2000 /READAHEAD:1

 ET> 9 lazy write workers? I haven't seen mentioned that high before.

Why not?

 ET> Is there something like a rule of thumb for this, or a relation
 ET> between how much disk intensive an application is, the disk
 ET> throughput and the number of lazy write workers? Is there a
 ET> trade-off, for example more lazy write workers need more memory?
 ET> If so, how much?

The optimasion was done at a time this computer was used as
- 3 lines node with mostly ISDN throughput
- developement mashine (edit/compile/debug...) with all lines running
- some other aktive tasks

HR>> Yes, disk caching is the most recent parameter on it.

 ET> I don't know what you mean with this. 

The optimasion was at least done with help another node to become the highest
possible transfer rate during an connect on both lines and running tosser in
background.

I'd found that throwing on the cache parameters has the most incredible effect 
on the transfer rates. I'd found values that are commonly nearst the physical
maximum (7950/15500 cps as sender and 7850/14500 as receiver of *.bmp)

Exchange of large *.bmp can kill the telko's convey station if both sides can
send with maximum speed on direct CAPI. :-)

Without the excessive optimasision step my transfer rate where more than 200
cps less.

For now this computer has lost all funtions other than holding the node 24h/7d 
online.

 ET> Can you clarify this? Didn't you use the cache command before?

Yes. But not this extensive testing to find the best parameters.

The first step to optimise is to optimise the config.sys:

maxwait=x			1 - 3, depending on RAM and CPU
				it is the first parameter to push up or slow down
				the mailer; 
priority_disk_io=no		let the mailer (and othert background) thread
				have higher priority to wirte/read to/from disk
				than forground threads
				must be NO if you would have a maximum throughput
				to your lines.

Both changes requires a system reboot


After that playing with the cache parameters can speed up the lines more.
Changes can be made without reboot. call cache.exe with the propper
parameters.


--- Sqed/32 1.15/development  477:
231/992
633/260
2501/209