The boxes are staying at 100% until all of the refreshes have either completed or failed. We are not isolating the WIQT or BusObj. WIGenerator and BusObj are running on both servers.
We had all ten users already logged in, then they refreshed in unison, we were testing concurrent refreshes. (We noticed that the boxes do spike when a user logs in)
I think there were only 10 WIQTs during the test. The security has a few levels, we are in the process of lowering to a max of two levels in the hierarchy.
Our Unix box is a HP 9000 and it is idling at about 30% (CPU, RAM, DISK, etc.).
Regards,
Michael Cole
______________________________ Reply Separator _________________________________
Date: 3/31/2000 12:54 PM
We did load testing with a similar configuration. Is it spiking to 100% or staying at 100%? Are you isolating the WIQT or BusObj processes on the node? Or are you enabling the WIGenerator and BusObj on both servers? The way we conducted our load testing was to ramp up the logins and then do the concurrent refreshes. The login was part of the intialization in the loadrunner scripts. The refresh was actually what we were testing (60 concurrent refreshes). We certainly didn’t see the CPU on the NT servers maxed for 10 users upon login, but we didn’t have them go directly into a refresh either. How many WIQTs are running at this time? What does the security domain look like when you’re trying this? In other words, what is the %utilization on your unix box?
Feel free to give me a call here at WDW and I we can compare notes.
Jodie
407-566-5177
Listserv Archives (BOB member since 2002-06-25)