Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: harry2121 on December 18, 2013, 08:38:14 AM
-
Interaction Workspace taking 900 + MB of Memory.Dont know whats the reason.
From Documents I got that Interaction Workspace uses between 185 MB (Voice only) and 230 MB (all features) of memory on
agent workstations.
Please help,its urgent :-\ :-\ :-\
-
Are there any customization? What says logs? What version are you using? Are you using HW or virtualized platform?
-
From the logs i got the following:
CollectionCount 0: 78406
CollectionCount 1: 8395
CollectionCount 2: 354
Total Memory: 504284440
Process Information :System.Diagnostics.Process (InteractionWorkspace)
physical memory usage: 916971520
base priority: 8
priority class: Normal
user processor time: 00:49:34.6582682
privileged processor time: 00:06:52.4666440
total processor time: 00:56:27.1249122
PagedSystemMemorySize64: 870960
PagedMemorySize64: 1180520448
threads Counts: 31
peakPagedMemorySize64: 1193598976
peakVirtualMemorySize64: 1894080512
peakWorkingSet64: 1142927360
workingSet64: 916971520
privateMemorySize64: 1180520448
virtualMemorySize64: 1869459456
which is much higher than normal
-
As asked by kubig, are you on real HW or using VMWare or similar?
-
using HW
-
Any one got any suggestions for this one
Please help :'( :'(
-
You still don't answer the question about IWS logs... any repeated request/event there, any exceptions or something like that? What Genesys support says? If the issue is so critical for you, you've contacted support of course I guess.
-
Plenty of stuff in release notes (PS: we currently has a similar problem with high CPU and memory utilisation) :-(
Release Number 8.1.401.24 [11/27/13] – Hot Fix
A memory leak, which occurred when an agent opened the Contact History or the Interaction History and then selected an interaction to view the interaction details, has been fixed. (IW-7669)
Release Number 8.1.401.19 [09/26/13] – Hot Fix
A memory leak that occurred during the handling of an Outbound interaction in Pull Preview mode has been fixed. (IW-7428)
Release Number 8.1.401.06 [05/30/13] – General
A memory leak has been fixed for the internal Instant Messaging feature. (ER# 323146705)
Release Number 8.1.401.06 [05/30/13] – General
For ASM campaigns, the loading of Call Processing Ports has been optimized to prevent memory usage issues. Previously in this scenario in environments that have a very large number of call processing ports visible to agents, there was a large usage of CPU bandwidth and memory. (ER# 320490447)
Interaction Workspace no longer has a memory leak in the following scenario: a supervisor/Team Lead executes a new operation on interaction(s) in a Workbin/Queue while a previous bulk operation is still in progress. (ER# 319927133)
Release Number 8.1.301.17 [12/21/12] – Hot Fix
Interaction Workspace no longer consumes a large amount of memory when it cannot connect to the backup SIP Server due to a SessionID mismatch between the primary and backup servers. Previously, if SIP Server was configured in Hot Standby and an HA Session ID mismatch occurred, Interaction Workspace memory increased constantly until an out-of-memory situation occurred and Interaction Workspace ended unexpectedly. (ER# 310843119)
It is now possible to upgrade Interaction Workspace to 8.1.3 by using ClickOnce on a Workstation where release 8.1.2, or earlier, was installed by using ClickOnce. Select the "64-bits deployment mode" option in the Interaction Workspace Deployment Manager. When this option is validated, the upgrade is permitted; however, the deployment is 64-bits ready instead of being forced to 32-bits, which results in higher memory consumption on 64-bits operating systems. (ER# 306600352)
Runs as a 32-bit application on 64-bit platforms—this feature decreases the memory footprint by 30%, which enables resources to be saved when Interaction Workspace runs in a Citrix environment
Release Number 8.1.300.17 [07/31/12] – General (Under Shipping Control)
The memory footprint of Interaction Workspace has been greatly decreased in environments where the quantity of information that is downloaded from Management Framework is a limiting factor. This typically occurs if one of the values of the teamcommunicator.list-filter-showing option is Agent. (ER# 299688471)
-
Definitively here you wont find a solution to such low level issue. Open an eSR on Genesys and they will ask a lot of environment informations to try to analyze your issue.
As Craig says, many issues with IWS as it is still not 100% finished.