Question Fat Client Parameters For Sx Gui 6.1.090

Charles Givens

New Member
We are a SX shop that runs GUI client mostly in a Citrix Environment.

We have about 15 PC's that we run for credit card processing. They are 2GB RAM PC's running Windows 8.1. Not huge machines at all.

I am having issues with performance, particularly when the user has to do a search on a group of records.

Can anyone give me some starting parameters that would I could adjust?

Current parameters are really default from Infor(SX). I have only adjust the TM and that helped some. It seems to me that the buffers need to be bigger for when it pulls down the records to then do the filtering. I am not an expert on that.

Our database resides on Linux server that also has our APP servers on them. We do have about 150 GUI clients, most of them Citrix connects, except these.

ANY guidance would be helpful.

Thanks

Charles
 

TheMadDBA

Active Member
Going to have to ask a few questions first :)

- What is your OpenEdge/Progress version?

- How many network hops between the client and the server?

- Are they really connecting client server or appserver?

- Is it just these clients that have the issue or all of them?

- What are the specs for the Linux host? Memory/Disk/CPU

- Current parameters used for the clients and the servers?

There are probably a ton of parameters you can change... how much any of them will help depends on the answers.
 

Charles Givens

New Member
Openedge 11.1
Several as some of the locations are connected via MPLS network. So on a minimun the resonse time is app 15 or 20 ms. There are at least 4 hops.
It is a client, that connects to the appserver. The appserver is on the same server as the database
Just the FAT clients. The Citrix clients are fine.
The Linux host is a VM server that has 4 processers, Disk space is plentiful, running on a SAN with mirrored drives. I am not swapping on the Linux box, so my memory seems to be fine.

The client has the following:
-inp 32000
-tok 4096
-rereadnolock
-D 500
-devevent
-filterocxevents
-s 1024
-mmax 65534
-nochkttnames
-rand 2
-d mdy
-cpinternal 1252
-TB 8
-pls

The Server:

12/11/15 Status: Startup Parameters
11:00:37

Maximum clients: 426
Maximum servers: 65
Maximum clients per server: 0
Lock table size: 100000 entries
Database buffers: 2228224 (8912896 kb)
Database alternate buffers: 0 (0 kb)
Excess shared memory: 208 kb
APW queue check time: 100 milliseconds
APW scan time: 1 seconds
APW buffers to scan: 3713
APW max writes / scan: 25
Spinlock tries before timeout: 24000
Before-image buffers: 20 (80 kb)
After-image buffers: 45 (180 kb)
Max number of JTA transactions: 100
LRU force skips: 0

Some other information on APW's user count,

21 Servers, 262 Users (17 Local, 245 Remote, 136 Batch),2 Apws

Thanks

Charles
 

TheMadDBA

Active Member
So both sets are thin clients... one set is just closer network wise.

You can try enabling message compression: Progress KB - How to enable message compression between the OpenEdge client and AppServer?

Not swapping on Linux doesn't mean a lot without knowing how much memory you have... Increasing -B and some of the other parameters might help with performance but you need to know how much free memory you really have. Some can help the DB and some can help the AppServers by decreasing physical IO.
 
Top