Courtesy Callback & Reporting Impacts on Wait Time/Average Speed of Answer
Hello,
With CVP Courtesy callback, if a caller selects to be called back and then hangs up, will that period of time be also considered in the Skill Group's wait times and average speed of answer? Or is wait time only considered when the caller is physically waiting on the phone?
Thanks,
Mike
Mike,
The caller is still considered "queued" for the duration. The CVP app that does the callback is run as a non-interruptable script, and keeps the ICM call active until the decision is made to call back the caller. ICM does not see this as any different from a regular queued call.
-Jameson
Similar Messages
-
We have CUIC 8.5 (2). I have a customer that would like to view a real-time display that shows the average speed of answer throughout the day. They would like it to be a running total. So by 4:00pm, they would like to know what the average speed of answer has been so far today. I know that the Call Type Real Time Display has the fields Answer Wait Time Today and Calls Answered Today. The Answer Wait Time is in seconds though. So, any idea how to change this into a chart to give them the information they are looking for? Thank you!
Mike,
The caller is still considered "queued" for the duration. The CVP app that does the callback is run as a non-interruptable script, and keeps the ICM call active until the decision is made to call back the caller. ICM does not see this as any different from a regular queued call.
-Jameson -
Waiting time report in Historical Reports tool
Hi all,
I'm looking for a report over caller waiting time. I can't mange to find such report in the Cisco Unified CCX Historical Reports tool. What shoul I look for?
Best regards
KristianThere are two different types of Abandonded calls that you will see in reports. The first is an Application abandon call. Eseentially this is a call that comes in to your application, does it's treatment but is ended without the caller being marked as handled. This could be due to say, a redirect out of the system or the caller terminating abruptly.
The second is a Contact Service Queue abandoned call. This is fairly straight forward, when a call enters the queue but terminates prior to being handled by an agent the call is marked abandoned.
Some things to watch out for:
I see this a lot, using the Call Redirect step without the Set Contact Info Step (marking the call as handled).
Having a voicemail opt out in queue, say someone is waiting in queue for 10 minutes and you give them the option to leave a voicemail then terminate the call.
Any time you manually terminate the caller, depending on circumstances and your script, you should mark the call as handled.
Lastly, you may want to catch on ContactInactiveException. Wherein you can do some logic to determine if you want to mark the call as handled or not.
HTH
Tanner -
UCCE 8.5 Courtesy Callback AWT
Hi all,
We have been battling with our Courtesy Callback reporting for couple of months now, Need to know how the Answer Wait Time (when enable CCB) is calculated , if you have the formula or exact definition how to calculate the answer wait time for Courtesy Callback options, Kindly let me know -
Appreciate your comments/feedbackThe recommended formula is below. However, as in our case, this doesn't seem to work in a multi-skilled environment.
ValidValue(((SkillGroup.X.RouterCallsQNow+1)
(ValidValue(SkillGroup.X.AvgHandledCallsTimeTo5,20))
/max(
SkillGroup.X.Ready,
(SkillGroup.X.TalkingIn
+
SkillGroup.X.TalkingOut
+
SkillGroup.X.TalkingOther))
),100) ValidValue(((SkillGroup.X.RouterCallsQNow+1)
(ValidValue(SkillGroup.X.AvgHandledCallsTimeTo5,20))
/max(
SkillGroup.X.Ready,
(SkillGroup.X.TalkingIn
+
SkillGroup.X.TalkingOut
+
SkillGroup.X.TalkingOther))
),100) -
What's wait time for ATT order nowadays?
I see from Apple's retail web site that most locations now have plenty of inventory.
Does anyone have any idea what the wait time is for iPhones ordered thru ATT?
I have a rather complocated change in my plan to make and feel that ATT will be better to handle than Apple store but I have a really narrow window of time to get one i.e. Aug 19-22.
Message was edited by: nedhamiltonGo to your AT&T store and ask for an iPhone 8G or 16G whatever floats your boat as far as music and video memory goes. When I went there, I paid for a pre-order $208.95. They pinged my credit card on July 19th and didn't charge it until it was shipped on 7/29 and picked up on 7/30. 7/31 they fulfilled the charge.
So it's at least 12 days yes. But if they don't have it in stock then it's that much of a wait time. -
Wallboard - Calculating daily average wait time
In Historical Reporting, if we look up a queue's average wait duration for the day we are given 5:34.
At the same time, if I pull up avgWaitDuration in RtCSQsSummary, I am given 190505. What number is this? Seconds? if in seconds, and the total calls answered for that queue is 248, then I should be able to divide 190505 by 248. When I do that, I get 768 seconds. 768 (12:48) is a far cry different from 334 (5:34). Where am I going wrong?Ok, I determined that the number is not actual ASA, but apparently "avg queue time". I assume this to mean the clock starts when the caller is placed in the queue, after completing the call tree.
I figured out how to calculate the time provided, and it matches the time in History Reporting for the "avg queue time". But the time we ACTUALLY want is the "avg speed to answer", as found in History Reporting for each queue.
What table would I find the ASA from the time the caller enters the call tree? -
The Average Wait Time of SQL instance "CONFIGMGRSEC" on computer " SEC_SITE_SERVER " is too high
I have a SCCM 2012 SP1 CU4 environment with SCOM monitoring installed.
I also do have 4 secondary sites installed below my primary. The secondaries are using SQL 2012 Express version default deployed using the secondary site installation.
My SCOM monitoring is generating tickets with the following message:
The Average Wait Time of SQL instance "CONFIGMGRSEC" on computer "<SEC_SITE_SERVER>" is too high
How can i solve this ? Or do I need to ignore this ?Never ignore messages, but tune them.
In this specific case you might want to take a look at this:
http://social.technet.microsoft.com/Forums/en-US/ffeefe0d-0ef7-49a3-862e-9be27989dc5d/scom2012-alert-sql-2008-db-average-wait-time-recompilationis-too-high?forum=operationsmanagergeneral
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Query identified as OracleOEM reporting a lot of CPU wait time
We use "Ignite" by Confio to monitor the wait time on our database and I have been watching a query for a while now and it seems to be consuming a lot of resources for what it is doing.
This is the query:
/* OracleOEM */
SELECT m.tablespace_name,
m.used_percent,
(m.tablespace_size - m.used_space)*t.block_size/1024/1024 mb_free
FROM dba_tablespace_usage_metrics m,
dba_tablespaces t,
v$parameter p
WHERE p.name='statistics_level'
AND p.value!='BASIC'
AND t.tablespace_name = m.tablespace_name
And this is the execution plan:
SELECT STATEMENT Optimizer=ALL_ROWS (Cost=152 Cardinality=17 Bytes=2193)
NESTED LOOPS (Cost=152 Cardinality=17 Bytes=2193)
NESTED LOOPS (Cost=152 Cardinality=17 Bytes=2125)
MERGE JOIN (CARTESIAN) (Cost=149 Cardinality=17 Bytes=1785)
HASH JOIN (Cost=2 Cardinality=1 Bytes=49)
FIXED TABLE (FULL) OF X$KSPPI (TABLE (FIXED)) (Cost=1 Cardinality=1 Bytes=31)
FIXED TABLE (FULL) OF X$KSPPCV (TABLE (FIXED)) (Cost=1 Cardinality=1897 Bytes=34146)
BUFFER (SORT) (Cost=148 Cardinality=502 Bytes=28112)
VIEW OF DBA_TABLESPACE_USAGE_METRICS (VIEW) (Cost=147 Cardinality=502 Bytes=28112)
SORT (UNIQUE) (Cost=147 Cardinality=502 Bytes=19122)
UNION-ALL
SORT (AGGREGATE) (Cardinality=1 Bytes=8)
TABLE ACCESS (BY INDEX ROWID) OF RECYCLEBIN$ (TABLE) (Cost=4 Cardinality=389 Bytes=3112)
INDEX (RANGE SCAN) OF RECYCLEBIN$_TS (INDEX) (Cost=1 Cardinality=388)
SORT (AGGREGATE) (Cardinality=1 Bytes=14)
FIXED TABLE (FULL) OF X$KTFBHC (TABLE (FIXED)) (Cost=0 Cardinality=1 Bytes=14)
SORT (AGGREGATE) (Cardinality=1 Bytes=8)
TABLE ACCESS (BY INDEX ROWID) OF RECYCLEBIN$ (TABLE) (Cost=4 Cardinality=389 Bytes=3112)
INDEX (RANGE SCAN) OF RECYCLEBIN$_TS (INDEX) (Cost=1 Cardinality=388)
SORT (AGGREGATE) (Cardinality=1 Bytes=14)
FIXED TABLE (FULL) OF X$KTFBHC (TABLE (FIXED)) (Cost=0 Cardinality=1 Bytes=14)
HASH (GROUP BY) (Cost=89 Cardinality=500 Bytes=19000)
MERGE JOIN (Cost=87 Cardinality=500 Bytes=19000)
TABLE ACCESS (CLUSTER) OF TS$ (CLUSTER) (Cost=86 Cardinality=426 Bytes=9372)
INDEX (FULL SCAN) OF I_TS# (INDEX (CLUSTER)) (Cost=1 Cardinality=1)
SORT (JOIN) (Cost=1 Cardinality=501 Bytes=8016)
FIXED TABLE (FULL) OF X$KTTEFINFO (TABLE (FIXED)) (Cost=0 Cardinality=501 Bytes=8016)
HASH (GROUP BY) (Cost=52 Cardinality=1 Bytes=38)
NESTED LOOPS (Cost=50 Cardinality=1 Bytes=38)
FIXED TABLE (FULL) OF X$KTTEFINFO (TABLE (FIXED)) (Cost=0 Cardinality=251 Bytes=4769)
TABLE ACCESS (CLUSTER) OF TS$ (CLUSTER) (Cost=1 Cardinality=1 Bytes=19)
INDEX (UNIQUE SCAN) OF I_TS# (INDEX (CLUSTER)) (Cost=1 Cardinality=1)
HASH (GROUP BY) (Cost=5 Cardinality=1 Bytes=84)
HASH JOIN (Cost=3 Cardinality=1 Bytes=84)
NESTED LOOPS
NESTED LOOPS (Cost=3 Cardinality=1 Bytes=65)
HASH JOIN (Cost=2 Cardinality=1 Bytes=49)
FIXED TABLE (FULL) OF X$KSPPI (TABLE (FIXED)) (Cost=1 Cardinality=1 Bytes=31)
FIXED TABLE (FULL) OF X$KSPPCV (TABLE (FIXED)) (Cost=1 Cardinality=1899 Bytes=34182)
INDEX (UNIQUE SCAN) OF I_TS1 (INDEX (UNIQUE)) (Cost=1 Cardinality=1)
TABLE ACCESS (BY INDEX ROWID) OF TS$ (CLUSTER) (Cost=1 Cardinality=1 Bytes=16)
FIXED TABLE (FULL) OF X$KTTEFINFO (TABLE (FIXED)) (Cost=0 Cardinality=251 Bytes=4769)
TABLE ACCESS (BY INDEX ROWID) OF TS$ (CLUSTER) (Cost=1 Cardinality=1 Bytes=20)
INDEX (UNIQUE SCAN) OF I_TS1 (INDEX (UNIQUE)) (Cost=1 Cardinality=1)
FIXED TABLE (FIXED INDEX) OF X$KCFISTSA (ind:1) (TABLE (FIXED)) (Cost=0 Cardinality=1 Bytes=4)
My question is two fold... does anybody know where in OEM you can control the execution of this query? I would like to reduce the frequency it is run, or if that is not a good idea does anybody have any ideas from a tuning perspective?
Ignite is reporting 1,440 executions, 621,776,455 buffer gets, and 2 hours of CPU wait time per day.
Thanks in advance,
ZackA typical question for this forum.
We use Oracle, we can't remember which version, and we can't be bothered to post it.
We don't know Oracle, so we use a third party product (Ignite from Confio) to perform redundant monitoring on our databases, which is already being performed by Oracle Enterprise Manager, for free.
Instead of trying to use the products which come with Oracle, we would like to wreck functionality, by tampering with things like frequency, and/or even adjusting Oracle provided queries, consequently invalidating our support contract for Oracle.
And, no, we are not aware, provided the database is doing nothing, queries like this one will automatically surface in the list of top <n> queries.
I would suggest you start to learn Oracle and dump Ignite. It is of no use to monitor your database with two tools, and OEM is fully integrated in Oracle.
Sybrand Bakker
Senior Oracle DBA -
SCOM2012 Alert: SQL 2008 DB Average Wait Time & Recompilationis too high
WE have SCOM 2012sp1 CU3 updated.
I receive the below critical alerts from SQL servers continuously, please help me to resolve this issue.
SQL 2008 DB Average Wait Time is too high
SQL DB 2008 SQL Recompilation is too highI don't know about anyone else but overriding those monitors and rules didn’t work for me, I had to override<o:p></o:p>
SQL Re-Compilation monitor for SQL 2012 DB Engine<o:p></o:p>
SQL Re-Compilation monitor for SQL 2008 DB Engine<o:p></o:p>
Average Wait Time monitor for SQL 2012 DB<o:p></o:p>
Average Wait Time monitor for SQL 2008 DB<o:p></o:p>
Now I am wondering if other monitors are valid as well in particular I have multiple alerts for<o:p></o:p>
Buffer Cache Hit Ratio monitor for SQL 2008 DB Engine is too low<o:p></o:p>
Page Life Expectancy (s) for 2008 DB Engine is too low<o:p></o:p>
is anyone else seeing these issues as well? -
PerfMon reporting dramatic disk access time increase on Oracle startup
Hi,
My oracle 10g (10.2.0.4) database is hosted on a windows 2003 server.
The datafiles are stored on a RAID1 disk array, on a dedicated partition : currently 30 gigs free out of 180, wich should not be a concern unless i'm wrong, because the datafiles were created as 10 Go files with no autogrowth. I add a new datafile whenever i need more room for my tables (alerts when 80% used).
Since 2 days i experience a dramatic performance loss :
The EM console reports nothing special (no alarms related to storage) apart from the need for more paginated memory.
I issue a reorg when the segmentation advisor suggests it.
My optimizer statistics are calculated by the default scheduled job.
The weird thing I noticed is that as soon as I start the database, there's a huge increase in disk activity even though no query at all is submitted to the database.
PerfMon reports Current Disk Queue Length > 1000 and disk access time > 3000 ms
CPU is 2% activity on the 4-cpus server.
I have plenty of spare memory (currently 3 Go used out of 16).
This is only a dev server for ETL processes, it has very few concurrent connections.
Any suggestions welcome.
AWR report is available here
http://min.us/mqnXQhd5Z
Edited by: user10799939 on 22 mars 2012 09:30Cache Sizes
~~~~~~~~~~~ Begin End
Buffer Cache: 1,296M 1,296M Std Block Size: 8K
Shared Pool Size: 160M 160M Log Buffer: 14,364K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 460,955.72 ; 2,477,358.63
Logical reads: 3,392.16 ; 18,230.80
Block changes: 6,451.93 ; 34,675.22
Physical reads: 2.92 ; 15.67
Physical writes: 394.52 ; 2,120.28
User calls: 1.69 ; 9.08
Parses: 3.31 ; 17.81
Hard parses: 0.17 ; 0.90
Sorts: 1.32 ; 7.09
Logons: 0.06 ; 0.31
Executes: 7.01 ; 37.68
Transactions: 0.19
% Blocks changed per Read: 190.20 ; Recursive Call %: 96.23
Rollback per transaction %: 0.30 ; Rows per Sort: 14.41
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.98 ; Redo NoWait %: 99.86
Buffer Hit %: 99.92 ; In-memory Sort %: 100.00
Library Hit %: 96.30 ; Soft Parse %: 94.96
Execute to Parse %: 52.74 ; Latch Hit %: 99.07
Parse CPU to Parse Elapsd %: 0.35 ; % Non-Parse CPU: 99.30
Shared Pool Statistics Begin End
Memory Usage %: 75.48 ; 75.51
% SQL with executions>1: 79.92 ; 85.03
% Memory for SQL w/exec>1: 77.07 ; 70.09
Top 5 Timed Events Avg %Total
~~~~~~~~~~~~~~~~~~ wait Call
Event Waits Time (s) (ms) Time Wait Class
db file sequential read 9,052 17,688 1954 51.3 ; User I/O
log file switch (checkpoint in 5,303 4,649 877 13.5 Configurat
log file switch completion 4,245 4,023 948 11.7 Configurat
wait for a undo record 32,393 3,531 109 10.3 ; Other
db file parallel write 18,771 3,437 183 10.0 System I/O Havent seen this much wait on average. For example 877ms for "log file switch" is over threshold. And other wait events too..
Time Model Statistics DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> Total time in database user-calls (DB Time): 34446.5s
-> Statistics including the word "background" measure background process
time, and so do not contribute to the DB time statistic
-> Ordered by % or DB time desc, Statistic name
Statistic Name Time (s) % of DB Time
sql execute elapsed time 4,008.5 ; 11.6
parse time elapsed 352.9 ; 1.0
hard parse elapsed time 352.7 ; 1.0
PL/SQL compilation elapsed time 120.1 ; .3
DB CPU 61.8 ; .2
failed parse elapsed time 21.3 ; .1
PL/SQL execution elapsed time 8.0 ; .0
connection management call elapsed time 0.0 ; .0
hard parse (sharing criteria) elapsed time 0.0 ; .0
repeated bind elapsed time 0.0 ; .0
hard parse (bind mismatch) elapsed time 0.0 ; .0
DB time 34,446.5 ; N/A
background elapsed time 14,889.7 ; N/A
background cpu time 39.0 ; N/A
Wait Class DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc
Avg
%Time Total Wait wait Waits
Wait Class Waits -outs Time (s) (ms) /txn
User I/O 10,515 .1 17,785 1691 15.8
Configuration 10,186 79.5 ; 8,865 870 15.3
System I/O 27,619 .0 8,774 318 41.6
Other 57,768 98.3 ; 6,915 120 87.0
Commit 2,634 88.6 ; 2,481 942 4.0
Concurrency 2,847 75.4 ; 2,240 787 4.3
Application 219 2.3 ; 23 105 0.3
Network 4,790 .0 0 0 7.2
------------------------------------------------------------- again seen, there is very high wait on User IO
Wait Events DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> s - second
-> cs - centisecond - 100th of a second
-> ms - millisecond - 1000th of a second
-> us - microsecond - 1000000th of a second
-> ordered by wait time desc, waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
db file sequential read 9,052 .0 17,688 1954 13.6
log file switch (checkpoint 5,303 78.0 ; 4,649 877 8.0
log file switch completion 4,245 89.2 ; 4,023 948 6.4
wait for a undo record 32,393 99.8 ; 3,531 109 48.8
db file parallel write 18,771 .0 3,437 183 28.3
wait for stopper event to be 24,203 99.8 ; 2,634 109 36.5
log file sync 2,634 88.6 ; 2,481 942 4.0
control file sequential read 7,356 .0 2,431 330 11.1
buffer busy waits 2,513 83.1 ; 2,173 865 3.8
log file parallel write 520 .0 1,566 3012 0.8
control file parallel write 840 .0 1,334 1588 1.3
rdbms ipc reply 172 91.3 ; 330 1916 0.3
enq: CF - contention 309 23.0 ; 268 867 0.5
log buffer space 638 28.5 ; 192 301 1.0
enq: PS - contention 52 23.1 ; 71 1362 0.1
db file scattered read 113 .0 67 590 0.2
os thread startup 76 77.6 ; 63 834 0.1
reliable message 57 78.9 ; 50 878 0.1
enq: RO - fast object reuse 22 22.7 ; 23 1038 0.0
latch free 537 .0 16 30 0.8
Streams AQ: qmn coordinator 3 100.0 ; 15 5005 0.0 Overstepping
Background Wait Events DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> ordered by wait time desc, waits desc (idle events last)
Avg
%Time Total Wait wait Waits
Event Waits -outs Time (s) (ms) /txn
db file parallel write 18,772 .0 3,437 183 28.3
events in waitclass Other 24,367 99.5 ; 3,010 124 36.7
control file sequential read 6,654 .0 2,333 351 10.0
log file parallel write 520 .0 1,566 3012 0.8
control file parallel write 840 .0 1,334 1588 1.3
buffer busy waits 899 94.2 ; 884 984 1.4
log file switch (checkpoint 206 82.0 ; 185 898 0.3
os thread startup 76 77.6 ; 63 834 0.1
log file switch completion 46 93.5 ; 45 982 0.1
log buffer space 158 31.0 ; 12 77 0.2
db file sequential read 62 .0 7 111 0.1
db file scattered read 20 .0 6 318 0.0
direct path read 660 .0 5 7 1.0
log file sequential read 66 .0 4 65 0.1
log file single write 66 .0 1 16 0.1
enq: RO - fast object reuse 2 .0 0 38 0.0
latch: cache buffers chains 3 .0 0 6 0.0
direct path write 660 .0 -5 -8 1.0
rdbms ipc message 9,052 87.5 ; 21,399 2364 13.6
pmon timer 1,318 90.4 ; 3,562 2703 2.0
Streams AQ: qmn coordinator 633 97.6 ; 3,546 5602 1.0
Streams AQ: waiting for time 77 61.0 ; 3,449 44795 0.1
PX Deq: Join ACK 21 .0 0 0 0.0 Again overshooting
Tablespace IO Stats DB/Inst: MDMPRJ/MDMPRJ Snaps: 2840-2841
-> ordered by IOs (Reads + Writes) desc
Tablespace
Av Av Av Av Buffer Av Buf
Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
UNDOTBS1
914 0 ###### 1.0 ; 1,368,515 383 2,534 863.2
MDMREF_INDICES
6,918 2 ###### 1.0 ; 11,086 3 0 0.0
SYSAUX
626 0 ###### 1.1 ; 1,804 1 0 0.0
SYSTEM
850 0 ###### 1.7 ; 296 0 0 0.0
MDMREF_DATA
293 0 712.3 ; 1.0 ; 274 0 0 0.0
MDMPRJ_ODS
198 0 72.1 ; 1.0 ; 198 0 0 0.0
FEU_VERT
33 0 61.5 ; 1.0 ; 33 0 0 0.0
USERS
33 0 31.5 ; 1.0 ; 33 0 0 0.0
------------------------------------------------------------- Now have a serious look at it. Av Rd(ms). Now for some tablespace value cannot event fit in window thats why its showing ##
According to oracle recommendation Av Rd(ms) shouldn't be greater then 20, if its goes over 20 then its considered to be an issue with IO subsystem. But as its seen that in your case its overshooting.
Now the question from my side
Have done any configuration changes?
I would suggest you to revert these changes asap and contact storage admin guys...
Hope this helps -
What is normal range for CPU Wait time Per Dispatch on Hyper-V 2012
Hello.
I am trying to troubleshoot some performance issues with an application that utilizes sql server, which runs in a Hyper-V Guest.
I have found that the ram, cpu, disk i/o all appear to be within normal range.
Before troubleshooting the sql end of things, I wanted to make make sure the vm isn't waiting for cpu time.
In Vmware, the metric for this is " CPU Ready". From what I can tell, the equivilant to this for Hyper-V on server 2012 is:
Hyper-V Hypervisor Virtual processor\CPU Wait time per dispatch.
I have fired this up and been monitoring it and found that the average is around 22,000, maximum 41,000.
The problem is, I have no idea if this is a normal or acceptable range. I can't seem to find any further information on actually interpreting this data, as to what is acceptable and what will cause performance issues etc..
Can anyone help enlighten me further on this?
ThanksHello.
I am trying to troubleshoot some performance issues with an application that utilizes sql server, which runs in a Hyper-V Guest.
I have found that the ram, cpu, disk i/o all appear to be within normal range.
Before troubleshooting the sql end of things, I wanted to make make sure the vm isn't waiting for cpu time.
In Vmware, the metric for this is " CPU Ready". From what I can tell, the equivilant to this for Hyper-V on server 2012 is:
Hyper-V Hypervisor Virtual processor\CPU Wait time per dispatch.
I have fired this up and been monitoring it and found that the average is around 22,000, maximum 41,000.
The problem is, I have no idea if this is a normal or acceptable range. I can't seem to find any further information on actually interpreting this data, as to what is acceptable and what will cause performance issues etc..
Can anyone help enlighten me further on this?
Thanks
Hi,
Hyper-V reports this metric is in nano seconds. So, your average is around 22-41 ms (milliseconds). This is GOOD.
Take this example:
This would be comparable to vCenter VM CPU Ready graph which displays VM CPU Ready time in milliseconds.
Note #1: This measures each virtual core presented to an individual VM. This will be different if you're not using hyper-threading on the host
Note #2: This is scaled to a factor of 0.001, so that the scale on the left is in milliseconds - which is commonly confused with a percentage scale, which is is NOT.
Not to dismiss CPU issues, but generally the first place I look when troubleshooting SQL on a VM is storage access/speed/performance, regardless of what hypervisor is being used. I would verify best practices like putting databases on separate physical
storage that ends up on separate spindles on the storage back end, same for logs, same for temp db, same for temp log,...
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) -
The wait time and resolve time is DEPLORABLE
Today is the third day in a row I have called into Verizon for the same issue. Day one spent 25 minutes on hold and NEVER got to speak to a person before I hung up. Day 2 Had a 15 minute hold before I spoke with someone, who then told me I had to speak to directv about something that was related to the Verizon part of my service, called directv confirmed it was a Verizon thing with a supervisor. Called BACK into Verizon waited for 30 minutes before I spoke with someone, got 30 seconds worth of talk in before another 15 minute hold, he came back on no apology not anything about the absolute rudeness and lack of courtesy. He told me they would have it fixed by the end of the day. Now here it is the nest day still not resolved, So I write this (while on hold waiting to have the call answered, its been 20 minutes) She finally did answer and was down right rude and through me right back on hold. I am so fed up with big business...
topdog wrote:
It may be your location. Here in Baltimore, there is little wait time and the representitives I get do not speak with accents.
Agree. I rarely wait more than a minute or two. And except at really off hours don't hear a foreign accent. NY area. -
Statspack report - Buffer Busy Waits on TEMP
I am trying to analyze a statspack report that covers an hour of production time when there was a lot of queries taking an unusally long time (2-3 min instead of < 1.5 seconds), this slow down was seen for about 30 minutes during that hour.
The unusall thing I am seeing is buffer busy waits on the TEMP tablespace and it looks like most of them are on the "file header block" for which I can't find any documentation on. There was only 13 disk sorts in this one hour so any ideas on why/how was the TEMP tablespace or just it's file header block so heavily used?
Here are some of the relevant secions of the statspack report. Thanks in advance for any help.
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 100.00 In-memory Sort %: 99.99
Library Hit %: 99.67 Soft Parse %: 99.54
Execute to Parse %: 1.13 Latch Hit %: 99.92
Parse CPU to Parse Elapsd %: 91.39 % Non-Parse CPU: 98.91
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
buffer busy waits--------------------------3,569------8,206--------35.76
CPU time-------------------------------------------------4,416------19.25
log file sync-----------------------------------34,024----3,779------16.47
direct path write------------------------------3,150------ 3,283--------14.31
log file parallel write--------------------------26,069-----1,100---------4.80
Tablespace
Av Av Av Av Buffer Av Buf
Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
OURAPP
---------81,928 ----23 ---1.3 ----1.4---------20,562---- 6-----------532---13.7
UNDOTBS1
---------13------------0 ---3.1------1.0---------15,801----4-----------219-----4.8
TEMP
--------2,979---------1----86.0----12.8--------3,240-----1-----------2,782-----######
SYSTEM
---------19------------ 0 ---5.3------1.0 --------2,372-----1-----------35-----1.1
Buffer wait Statistics for DB
-> ordered by wait time desc, waits desc
Tot Wait Avg
Class Waits Time (s) Time (ms)
file header block ----2,781---8,393-------3,018
data block----------- 538--------7----------- 14
undo header--------- 91--------1----------- 11
undo block ----------128--------0----------- 0
segment header ---- 26------- 0----------- 0We do have Diagnostic pack license but in this situation how can i generate AWR report for Standby(Active Dataguard) ? Hence we have scheduled Statspack in Cronjob on Primary which connects to Standby and take snapshots.
I have used ASH on Standby(Active Dataguard) since it resides in Standby memory. At the same time i cannot take ASH report for standby since it fetches it from AWR ASH(DBA_HIST_ACTIVE_SESS_HISTORY) of Primary.
SQL> select tablespace_name,file_name,bytes/1024/1024 MB from dba_data_files where tablespace_name like 'UNDOTBS%';
TABLESPACE_NAME FILE_NAME MB
UNDOTBS1 /s01/p15/p15_undotbs101.dbf 10240
UNDOTBS2 /s01/p15/p15_undotbs201.dbf 10240Please let me know if you need any more information. -
Uccx 9.0 expected wait time returns a -1 value
Guys I am trying to use the expected wait time feature in UCCX, however the value returned is -1 each time this step is executed. All the other feature such as average wait time etc all works, its just the expected wait time that doesnt. Any ideas please?
During your tests, the call activating the script you are debugging is actually in queue and with a real wait time?
I could find any related bug, can you check this links:
Link1 -- Link2
I will try to find additional information.
Rolando Valenzuela -
Answer wait time SG vs Call type
IPCCE 7.1 CVP 3.1 .We had a big issue regarding call type reports and skill group reports, exactly regarding the ASA. why the answer wait time is huge in skill group comparing to call type, our scenario is little bit different as we have five call types feeding the same skill group based on the customers category, and every queue to skill group node has different priority, so we need to know why answer wait time is hugely different in skill group compared to the call type.
attached is one of the five scripts, all the rest of them are the same and. each one is maped to one call toype.attached are clear scripts
You have your Send to VRU in the wrong place, in my opinion.
With CVP, the first thing to have is an explicit "Send To VRU". For calls from the PSTN, failure in this should go to an End node, which forces survivability on the gateway to play the error message. For warm transfer calls, the best is probably Release.
No point in going further if Send to VRU fails.
Then I would set the ECC variables required for your microapps.
Once you have this, then go to your Call Type node - to set the "queuing" call type. I don't like to rely on the call type that the script is scheduled against, because you normally have to peel off calls for holidays, out of hours and so on. I like to make it obvious what's being counted by the queuing call type.
Finally, go into your Queue To Skill Group.
Be aware that RONA will mess up the call type stats a little - they will be counted as Other (which includes short calls, but they are counted separately so it's possible to see the RONAs). I would rather not set a call type on the RONAs as some do, as this will mean that they are in "Flow Out" and the stats are messed up even further.
For failures out of Q2SG, I like to send them to a script where I set an "error" call type to count and return the error label on the CVP RC.
Everyone has different ideas ...
Regards,
Geoff
Maybe you are looking for
-
I m not able to debug into a BADI, though I tried putting a break point in the include for the BADI as well as tried using break-point 'MYUSERID'. It still doesnt work
-
How to combine the line items of 2 Sales orders into 1 delivry
how to combine the line items of 2 Sales orders into 1 delivry and their process, pre-requisites and tcode
-
If anyone knows what my next step is, please help! Thanks
-
Change/Delete Existing Pricing Condition Type
Hello I have a manu Pricing Condition Type and a rate(obtained from custom source) was inserted pro-grammatically into this line item whenever the new line item was added into the basket using CRM_ISA_BASKET_ITEMS badi. When the user changes the Qty
-
How Oracle works on the principle of grid computing?How is the use of g justified ?