This post is more than 5 years old
31 Posts
0
221882
August 21st, 2013 11:00
Slow vWorkspace Environment
Hi Guys,
we have an issue that the start of an application from clicking on one till the application is fully available takes too much time.
Especially i want to discuss the long wait time beteween clicking on an app in AppPortal Client and the Quest "Starting" Box.
Everytime it takes 20-30 Sec. to start the connection, sometimes more.
In this time AppPortal stops responding and waiting for informations from the Broker. (and its not a client side issue, because i have the same behavior on every client)
From WebAccess we can see that first it takes too much time to load the .pit-File and after that also takes too much time too load the Connection.
Whats your experience with these Perfomance in vWorkspace and any Best Practices to get the most out of a vWorkspace Environment ?
I just think our Broker is fully loaded with Apps and Copmputer Groups and thats why the performance is going down. Are there any suggested limits ?
On the Broker we have total of:
- 115 Computer Groups
- 188 Computers/VDIs (Parallels)
- 810 Managed Applications
From the Resource (CPU/RAM) Usage the Servers are not at the limit and have many Resources free.
Any Ideas ?
Many Thanks,
Attiq
DELL-Andrew W1
378 Posts
0
August 22nd, 2013 13:00
That's fine, I'm adding more apps to mine as we speak.
I know of many customers with way more Users/VDIs but I've never seen that many Applications.
DELL-Andrew W1
378 Posts
0
August 21st, 2013 12:00
Hello Attiq,
A Connection Broker log will show how long the broker is taking to process the request and what it is doing in the meantime.
A good indicator is purely how long it takes to fill the 10mb file.
How many Brokers have you got?
Do you have a dedicated SQL Server just for vWorkspace? Is Reporting enabled?
Thanks, Andrew
DELL-Andrew W1
378 Posts
0
August 22nd, 2013 08:00
Hi,
What I'm looking for in the log is
CDbManager:connection held XXXX ms
This will help show if it is the SQL that is the bottleneck or the Broker.
Thanks, Andrew.
ashad1
31 Posts
0
August 22nd, 2013 08:00
Hi,
i dont get some real infromations from the log. The times mentioned in the logs are quite the same like in our other environment, but there the behavior is much faster.
For the "Problem"-Environment we have one Broker and the database is on a shared instance.
Reporting is not enabled.
Is in this case better to have a cluster of two or more brokers ?
Thanks,
Attiq
ashad1
31 Posts
0
August 22nd, 2013 09:00
Hi,
i can see different times in the log from 40ms to 160ms and sometimes more.
Here is a part from the log:
20-Aug-2013 15:06:58 - 1416 : 1424 - CDbManager:reusing conn=0x06dd3c78 (50)
20-Aug-2013 15:06:58 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:06:58 - 1416 : 1424 - CDbManager:keeping conn=0x06dd3c78 (50, lastCount=49)
20-Aug-2013 15:06:58 - 1416 : 1424 - CDbManager:connection held 68 ms
20-Aug-2013 15:06:58 - 1416 : 1424 - ### Finished collection message (msec=148)
20-Aug-2013 15:06:58 - 1416 : 1424 - ### Accepted collection message...
20-Aug-2013 15:06:58 - 1416 : 1424 - CDbManager:reusing conn=0x06dd3c78 (50)
20-Aug-2013 15:06:58 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:keeping conn=0x06dd3c78 (50, lastCount=49)
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:connection held 65 ms
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Finished collection message (msec=144)
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Accepted collection message...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:reusing conn=0x06dd3c78 (50)
20-Aug-2013 15:06:59 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:keeping conn=0x06dd3c78 (50, lastCount=49)
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:connection held 152 ms
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Finished collection message (msec=231)
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Accepted collection message...
20-Aug-2013 15:06:59 - 1416 : 1440 - CDbManager:reusing conn=0x06dd3c78 (50)
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:reusing conn=0x06dd4898 (50)
20-Aug-2013 15:06:59 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:06:59 - 1416 : 1440 - Getting the next action...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:keeping conn=0x06dd4898 (50, lastCount=48)
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:connection held 88 ms
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Finished collection message (msec=183)
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Accepted collection message...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:reusing conn=0x06dd4898 (50)
20-Aug-2013 15:06:59 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:06:59 - 1416 : 1440 - Getting the next action...
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:keeping conn=0x06dd4898 (50, lastCount=48)
20-Aug-2013 15:06:59 - 1416 : 1424 - CDbManager:connection held 90 ms
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Finished collection message (msec=213)
20-Aug-2013 15:06:59 - 1416 : 1424 - ### Accepted collection message...
20-Aug-2013 15:06:59 - 1416 : 1440 - CDbManager:keeping conn=0x06dd3c78 (50, lastCount=49)
20-Aug-2013 15:07:00 - 1416 : 1424 - CDbManager:reusing conn=0x06dd3c78 (50)
20-Aug-2013 15:07:00 - 1416 : 1440 - CDbManager:connection held 545 ms
20-Aug-2013 15:07:00 - 1416 : 1424 - Getting the remote computer state...
20-Aug-2013 15:07:00 - 1416 : 1424 - CDbManager:keeping conn=0x06dd3c78 (50, lastCount=49)
20-Aug-2013 15:07:00 - 1416 : 1424 - CDbManager:connection held 114 ms
20-Aug-2013 15:07:00 - 1416 : 1424 - ### Finished collection message (msec=255)
The time is not constant.
Br,
Attiq
ashad1
31 Posts
0
August 22nd, 2013 13:00
Sorry.. this is our one and only environment with such big amount of customers and apps.
our other environemnt have about 260 VDIs and 100 Apps in just 35 Groups.
Thats why i just want to hear if maybe somebody have or had problems wich súch amount of Data...
Thanks,
Attiq
DELL-Andrew W1
378 Posts
0
August 22nd, 2013 13:00
Hello,
That shows your DB is fairly slow to respond but not really slow enough to explain the big wait.
In your faster environment, do you have a similar amount of managed apps ?
810 Managed Applications is a lot more than I normally see so I'm wondering if the SQL query isn't be very effecient when checking if you are allowed to launch the app.
Let me know, I can go and add about 780 more apps to mine to see if that is the problem