Windows Terminal Server Fact vs. Fiction Bernard Douthit & Jonathan Steel

Transcription

1 FINDINGS Guidelines for Implementing OneWorld Technology J.D. EDWARDS RESULTS SERIES Implementing OneWorld Technology Windows Terminal Server Fact vs. Fiction Bernard Douthit & Jonathan Steel Technology Demographic Table Product OneWorld B732.1 Version Service Pak 8 Platform/OS Intel NT Industry Application Database SQL Server 7.0 Keywords Windows Terminal Server Date September, 9, 1998? J.D. Edwards World Solutions Company. All Rights Reserved 05/24/01

2 Document Title in Header Executive Summary Microsoft new Windows Terminal Server is currently a central part of J.D. Edwards recommended strategy for customers running OneWorld over Wide Area Networks. Therefore it is incumbent upon us to test both stability and scalability. We have run several tests to ascertain this stability and scalability using both manual entry and a macro scripting tool for repeated tests. Our Testing Environment is as follows: OneWorld Version B732.1 with Service Pack 8 Enterprise Server Compaq??? Intel/NT Deployment Server Terminal Server Workstation PC s Database SQL Server 7.0 Beta Terminal Manager ICA Metaframe 4 x 233 Pentium, 1 GB RAM 166 Pentium 64 MB RAM What we believe our tests show is that Windows Terminal Server combined with Citrix s Metaframe Product is a very reliable and scalable solution for those customers needing remote access for up to 40 remote users on one Terminal Server. Scripting Tool We used a shareware scripting product called Macro Scheduler. For our tests, this product had all of the necessary functionality that WinRunner has, yet uses up much less hard disk space and RAM. Since whatever scripting tool we used would have to be copied to a separate directory for each of the sessions we used, we found that this smaller tool was much more useful. Furthermore since WinRunner cannot recognize Objects in Windows Terminal Server, it would give us no advantages over Macro Scheduler. Preliminary Findings Our preliminary tests have shown a significant amount of instability for WTS with large numbers of sessions running concurrently. We are most concerned with the fact that one hung session may possibly cause all WTS sessions to crash. J.D. Edwards Results Series Findings Page 1

3 First Test - Signon Our first test involved a OneWorld login entered manually over 50 sessions. It was our intention to test the CPU and memory usage of the Terminal Server during logon. We created 45 separate sessions on one client workstation. In each session we logged onto OneWorld. We closely monitored Terminal Server memory and CPU usage. Logging on 45 sessions in this test took under 2 minutes for all. Second Test SOE 1 - Kernel Our second set of tests were done setting the kernel processes to 1 on the Enterprise Server and mapping master business functions to that machine as well. We should note that these tests were done with SQL Server 6.5, which does not have record level locking (7.0 does)., so for those customers who may not be upgrading to 7.0 for a while, these results, and a Kernel setting of 1 may be more valid than our other results. General assumptions about WTS using large amounts of RAM per session are borne out in these tests. On average, as you can see WTS uses about 40 MB of RAM per each incremental user. In this example you can see that RAM is much more of a constraint that is CPU usage. The peak CPU usage in the test of 10 users only 22% for the terminal server and 25% for the Enterprise server. 1 U SER PROCESSOR AVG PROCESSOR RANGE MEMORY TIME ( S E C) T ERMINAL S ERVER 8% 3-11% 78, ENTERPRISE SERVER 5% 3-12% 850,900 MEMORY 78,404 2 USER TERMINAL SERVER 10% 7-16%, ENTERPRISE SERVER 15% 11-20% 852,408 3 USER TERMINAL SERVER 15% % 150, ENTERPRISE SERVER 20% 15-24% 854,048 5 USERS TERMINAL SERVER 17% 19-24% 221, ENTERPRISE SERVER 22% 6 USERS TERMINAL SERVER 17% 10-19% 257, ENTERPRISE SERVER 22% 20-24% 859, U SERS TERMINAL SERVE R 15% 12-22% 400, ENTERPRISE SERVER 23% 19-25% 867,580

4 Third Test SOE 4 Kernels MBF Mapped to ES Our third set of tests and most important involve the change in setting on the Enterprise Server to 4 Kernels which we found to be most efficient, and the OCM Mapping of Sales Order Entry Master Business Function B to the Enterprise Server. Note that the use of a logic server for WTS is highly recommended. In fact, if customers are planning on running more than 5 concurrent users they should map all Master Business Functions to a logic server. What we believe these tests show is the true reliability and scalability of Terminal Server. We were able to run up to 50 users with only 1 GB of RAM on our Terminal Server. Although this test did run very slow because of paging, it did run successfully as is shown below. Sales Order Entry Test 5 U SERS PROCESSOR AVG PROCESSOR RANGE MEMORY TIME ( S E C) T ERMINAL S ERVER , ENTERPRISE SERVER 14% , USERS TERMINAL SERVER 14% , ENTERPRISE SERVER 24% 1-52% 1,105, USERS TERMINAL SERVER 18% 3-20% 654,900 ENTERPRISE SERVER 37% 1-77% 1,117, USERS TERMINAL SERVER 30% 24-35% 822,688 ENTERPRISE SERVER 40% 1-70% 1,112, USERS TERMINAL SERVER 30% 17-65% 1,253,408 ENTERPRISE SERVER 57% 45-70% 1,223, U SERS TERMINAL SERVER 32% 25-40% 1,562, ENTERPRISE SERVER 50 U SERS TERMINAL SERVER 40% 25-40% 1,932, ENTERPRISE SERVER

5 Fourth Test 100 User Signon S OFTWARE F OR A C HANGING W ORLD? J.D. Edwards World Solutions Company World Headquarters One Technology Way Denver, Colorado 80237, USA / J.D. Edwards U.K. Ltd. Serving Europe, the Middle East, and Africa Oxford Road Stokenchurch, High Wycombe Buckinghamshire HP14 3AD, United Kingdom J.D. Edwards World Solutions Company Serving Latin America and the Caribbean 800 Douglas Entrance Coral Gables, Florida 33134, USA J.D. Edwards Hong Kong Limited Serving Asia Pacific Unit A, 24 th Floor, Entertainment Building 30 Queen s Road Central, Hong Kong The materials contained herein are summary in nature, subject to change, and intended for general information only. J.D. Edwards is a registered trademark of J.D. Edwards & Company. The names of all other products and services of J.D. Edwards used herein are trademarks or registered trademarks of J.D. Edwards World Source Company. All other product names used are trademarks or registered trademarks of their respective owners.? J.D. Edwards World Source Company 1998 One or more U.S. Patent Applications are pending for inventions used in the production of OneWorld.