RE: [ifxmaillist] Slow Connection from clients
This is my understanding of the Informix position on NT and the consequences of multiple applications placed on one NT Server. There are other software suppliers that have similar recommendations. Informix recommend that the database server is a member server, not a PDC or BDC. Moreover IDS should be the only application on the server. The installation should be local (everything in the local registry) and the user validation is done at database connection time on the local user manager table. Here you have the same NT server being the Database server, application server and PDC. The result of all these functions is expected to be poor performance! This is what you are observing, and from my experience with Informix on NT, you are getting very good connection time. When we first installed a customers application - database server only, application server was BDC, Domain install - we were getting 14 second minimum database connection time. We went around in circles a number of times with Informix Support and found we needed to change the configuration. Our current best with 35 users in the user manager table is about 4 seconds connect time. NT does not handle multiple applications on the same server well. When a connection is required, your have your application, the database server, calls to the Windows registry, the return of the entire user manager table (I am told this must be done in NT), plus tcpip activity. All this on the same server takes time - much longer than if you had multiple servers. For NT it is advisable to keep the registry small and the user manager table small. To determine the problem you would need to do some work to find out which of these is taking the most time and rectify that situation. The clue came for us when we set up a Y2K testing configuration in its own domain with only 4 users in the user manager table, and no other activity. Less than 2 seconds connect time. When you choose a platform there are limits of that platform that you have to live with. This is also true for flavours of Unix. In NT the OS limitations make connections to the database slow. Murray Wood -----Original Message----- From: Bertoni Andrea [mailto:bertoni@tecnest.it] Sent: Thursday, March 30, 2000 7:34 PM To: murray@quanta.co.nz Subject: RE: [ifxmaillist] Slow Connection from clients The server is essentially a database server and an application server (the c/s appl that's slow using client connections). It's a PDC with WINS server, simple tcp/ip services,microsoft print services,remote access. Not many PC on the LAN (4 clients). I think there are no more than 10 users accounts. No TSE on the network. The database server is not under pressure. No problem pinging ip/addresses nor aliases (immediate reply). Really strange! Andrea -----Original Message----- From: Murray Wood [mailto:murray@quanta.co.nz] Sent: mercoled' 29 marzo 2000 23.17 To: 'KuKi'; informix-list@iiug.org Subject: RE: [ifxmaillist] Slow Connection from clients Andrea Is IDS the only application / function running on that NT server? or Is this also the PDC? Where is the user verification being done - on the Database Server ot the PDC? How busy is the PDC? How busy is the Database Server? How many users in the NT database (usrmgr?) where the Users are authenticated? (This may be the real problem). Is there any NT Terminal Server Edition machine involved? Murray Wood -----Original Message----- From: owner-ifxmaillist@quanta.co.nz [mailto:owner-ifxmaillist@quanta.co.nz]On Behalf Of KuKi Sent: Wednesday, March 29, 2000 8:29 PM To: informix-list@iiug.org Subject: [ifxmaillist] Slow Connection from clients LAN Scenario: Nt server 4.0 SP4; IDS Workgroup Ed. 7.31.TC3 Primary Domain Controller, Wins and Simple TCP/Ip Service installed Some Win NT Workstation clients. No problems connecting to the Informix server from the application installed on the server (immediate connection). 6-7 sec of delay connecting from the client apps. Then normal performance using the application. We've tried: Defining an Informix/Informix user (which is the predefined IDS account ) as a local (workstation) user on the clients. Connecting to the server using the IP address (not the alias) ....but we've an immediate reply also pinging the host alias, not only pinging the server IP address... I think that our setnet32 connecting parms are correct (infact we've a connection). I think the problem could be in "resolving" something. But "something" what? Any suggestion will be highly appreciated Andrea