Have a look: Optimal View A after installation and Optimal View B after 30 minutes quick customization. (Some people do not believe me, ok I agree it took a couple of hours. )

Deployment

What ratios should I use in my configuration files to maximize OptimalView performance in Windows?

If you have a Uniface web application, you could use this information for deployment time.

; Use only one of the following groups of settings. (Note that a semicolon comments-out a group of settings.)
; Low Usage Settings
MAXSESSIONS=3
MINSESSIONS=1
SESSIONWAIT=30
POLLINGTIME=10
MAXAPPIDLETIME=120
MAXSESIDLETIME=60
RESOURCEDIR=C:\optimalview\application\webuser\Resource

; High Usage Settings
;MAXSESSIONS=10
;MINSESSIONS=3
;SESSIONWAIT=120
;Fast polling delays WAM error occurrence
;POLLINGTIME=1
;MAXAPPIDLETIME=7200
;MAXSESIDLETIME=1200

MAXSESSIONS=64 is considered reasonable maximum based on number of available windows (program) handles
MAXSESSIONS=110 is considered absolute maximum based on COMCTL32.DLL common controls failing after reaching 111 ASV's.

ISAPI-URD TCP, Web server, and Application Server (ASV) time relations

UPSVINACTIVETCP = 15
(15 minutes) No TCP communication, terminate process

UPSVINACTIVETCP > TIMEOUT 300
(5 minutes) Processing time exceeded, terminate process

TIMEOUT > SESSIONWAIT 120
(2 minutes) Session time exceeded, abort request

POLLINGTIME=1
Every polling period, check session threads and terminate timeouts

MAXSESIDLETIME 1200
(20 minutes) MW Session idle expiration, abort threads to MINSESSIONS

MAXSESIDLETIME > MAXAPPIDLETIME 7200
(2 hours) Max ASV idle, terminate after this amount

MAXSESIDLETIME > Web server timeout 900
(15 minutes) No HTTP activity, release session

**Notes:
UPSVINACTIVETCP can be modified in the [TCP] section of PSYS.INI and USYS.INI files.
Web server timeout can be modified under IIS Web site, Properties.

Realized timings:
15 > 5 > 2/15 at 20 minute cycles, no greater than 2 hours at 1-minute check intervals

The first three settings under the ISAPI-URD heading describe the ability to process the request within the given middleware threads. If you haven't communicated with the network in 15 minutes, then terminate. If you can't complete the data request and issue ASV processes within 5 minutes, then terminate. Give ASP 2 minutes to respond. Otherwise, the Web server will expire at 900 seconds (15minutes).

The last three settings under the ISAPI-URD heading describe ISAPI filter thread management. Every polling period, check for sessions older than 20 minutes or middleware threads over 2 hours and terminate them.