Slow video playback after upgrading to ati 9200 card

Just upgraded my graphics card to the PCI ATI 9200 but now I have slower video playback than I had with the OEM Geforce AGP card. Does anyone know why this has happened? I thought I was gonna get better playback by upgrading
G4 Quicksilver 733 896mb ram Mac OS X (10.3.9)

Hi,
Well, you have me scratching my head, that's a real puzzle.
Try an Open Firmware re-set, do the 're-set all' procedure:
http://docs.info.apple.com/article.html?artnum=42642
BTW, ATI (and OWC) has just released this info on their 9600 video card, meaning it's not so good for G4's:
Knowledge Base
ATI Customer Care > Product Information > Specifications, Features, Comparisons >
737-21888: Radeon 9600 PRO PC & MAC Edition list of supported system configurations
The information in this article applies to the following configurations:
Radeon® 9600 PRO PC & MAC Edition
"Quicksilver" Power Mac G4 model
"Quicksilver 2002" Power Mac G4 model
"Digital Audio" Power Mac G4 model
The Radeon 9600 Mac & PC Edition is not compatible with the "Quicksilver", "Quicksilver 2002" or the "Digital Audio" PowerMac G4. If a Radeon 9600 Mac & PC Edition board is installed in one of these systems the result is a blank display.
For assistance in differentiating Power Mac G4 models, please refer to Apple Article 58418.
Regards,
Dave

Similar Messages

Slow video playback after reinstalling Geforce2 MX card

Ok, reinstalled (took out the 9200 card) my Geforce2Mx card and now everything is in super slow motion - video, scrolling, typing, opening and closing of apps, pull down menus, loading of web pages - everything. It's like being back on an old SE30 and now even that seems fast to what is happening now. What did I do wrong? Tried rebooting a few times and resetting pram with no better results.
G4 Mac OS X (10.3.9)
Posts: 536
From: Vancouver, Canada
Registered: Dec 30, 2005
Re: Slow video playback after upgrading to ati 9200 card
Posted: Apr 10, 2006 11:56 PM
in response to: G J
Press the button near the battery on your logic board, it will reset the PMU, which might help.
Gigabit Ethernet G4 upgraded 1.2Ghz, 120GB HD, 10GB HD, 1GB RAM Mac OS X (10.4.6) ibook G4 1.42Ghz, 80GB HD, 786 MB RAM, 1GB iPod Shuffle
Tried that also with no results. Also repaired permissions. What could have happened to the machine to do that?
G4 Mac OS X (10.3.9)

Installed the modified Radeon ATI 9600 Pro for G5 Edition card and I still have the same slow video playback results. However when I boot up from another internal hard drive I do not have the video problems. Everything works just fine. Both of my hard drives had no video problems before screwing around with the ATI cards and now the one still has the problems with the video playback. This one also has Classic on it and Classic also runs slow. BTW I don't know if this has anything to do with it but when I ran a search result for "ATI" no files are installed on that 2nd hard drive which is playing video and loading pages with no problems. Would trashing all those ATI files on the slow drive do anything to help? Or is this just a coincidence?

Choppy iPhone video playback after upgrading to 10.5 + QuickTime 7.6.9

Hi,
I recently upgraded from 10.4 to 10.5 on my Powerbook G4. I used the "Archive and Install" option. After updating all software to the latest (10.5.8 OSX + 7.6.9 QuickTime), I noticed that the playback of the videos shot with my iPhone 3GS becomes extremely choppy (jumps combined with slow-mo). Based on the what's in "Previous System", I was using QT 7.6.4 with OS 10.4, which didn't have this playback issue.
I found several posts related to similar issues in the forum, and tried the following suggestions without success:
(1) removing all third party plug-ins from /Library/QuickTime;
(2) repair permissions with Disk Utility;
(3) installing Perian;
None of the above made a difference. Just for the heck of it, I tried "su" in Terminal and moved "QuickTimeH264.component" to "QuickTimeH264.component.bkp". Surprisingly this made the playback a lot better (all the iPhone clips are H264+ACC). So I'm guessing somehow the QT H264 component is not working properly for me, but what is QT using instead to play those videos after I renamed the component? It shouldn't be any of the third-party plug-ins since I tried removing all the third-party stuff at the same time, and the videos still played fine. I'd like to get to the bottom of this as I'm a little uneasy about re-naming the H264 component.
I hope someone more QT savvy can diagnose the problem based on what I've tried and make new suggestions. Granted my machine is a bit long in the tooth but it's still decently powered (1.67 GHz, 1.5 GB RAM, 320GB HDD) and the videos played fine before the "upgrade".
Is it worth doing a clean re-install of 10.5 as opposed to the "archive and install"? It's a pain obviously to have to re-install all the apps but I'm willing to try it if it could reasonably make a difference.
Thanks in advance!

The problem is that you moved your Mail application to a sub-folder in your Applications folder, and you are running an older copy of Mail.
From your crash report it shows your path is to a different folder then the default folder:
Path: /Applications/Mail Apps/Mail.app/Contents/MacOS/Mail
It also shows that you are not running the correct version of Mail (should be version 3.5 (930.3):
Version: 3.5 (929.4)
Check out this article:
http://support.apple.com/kb/TS2486
The short of it is that you may have two copies of Mail on your system. When 10.5.6 installed, it may not have updated Mail correctly. Look to see if you have another copy of Mail in your Applications folder, and if so run it and check it's version from the 'About Mail' menu option, it should be 3.5 (930.0). My recommendation is to remove any copy of mail that is not in /Applications (if there is no version of Mail in Applications, move the one you have in Mail Apps back) and run the Mail Update referenced in the article above.

Slow down Database after upgrading to 10.2.0.5

Hi
I am having performance problems after upgrading to 10.2.0.5
At the beginning I thought the problem was sga too smalle ( ini: 598M , now 1408M ) but even after recreating the database with the new value the problem remains.
I am sending reports so that someone could give me an idea.
Thanks in advance!
DETAILED ADDM REPORT FOR TASK 'TASK_240' WITH ID 240
Analysis Period: 22-JUN-2011 from 08:34:06 to 16:00:13
Database ID/Instance: 2462860799/1
Database/Instance Names: DXT/DXT
Host Name: thoracle
Database Version: 10.2.0.5.0
Snapshot Range: from 71 to 78
Database Time: 6726 seconds
Average Database Load: .3 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FINDING 1: 38% impact (2540 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RECOMMENDATION 3: SQL Tuning, 14% benefit (926 seconds)
ACTION: Use bigger fetch arrays while fetching results from the SELECT
statement with SQL_ID "7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
FINDING 2: 37% impact (2508 seconds)
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RATIONALE: Average CPU used per execution was 0.036 seconds.
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RATIONALE: Average CPU used per execution was 32 seconds.
RECOMMENDATION 3: SQL Tuning, 5.8% benefit (390 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cbtd2nt52qn1c".
RELEVANT OBJECT: SQL statement with SQL_ID cbtd2nt52qn1c and
PLAN_HASH 2897530229
Select DAE_.ROWID, DAE_.*, HAE_.*
From THPR.GACCENTRYD DAE_, THPR.GACCENTRY HAE_ Where ((HAE_.TYP_0(+)
= DAE_.TYP_0) AND (HAE_.NUM_0(+) = DAE_.NUM_0))
And HAE_.CPY_0 = :1 And HAE_.ACCDAT_0 >= :2 And HAE_.ACCDAT_0 <= :3
And DAE_.ACC_0 = :4 And HAE_.FCY_0 >= :5 And HAE_.FCY_0 <= :6
Order by DAE_.BPR_0,DAE_.CUR_0,DAE_.ACC_0
RATIONALE: SQL statement with SQL_ID "cbtd2nt52qn1c" was executed 12980
times and had an average elapsed time of 0.03 seconds.
RATIONALE: Average CPU used per execution was 0.029 seconds.
RECOMMENDATION 4: SQL Tuning, 2.1% benefit (138 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"33t7fszkr29gy".
RELEVANT OBJECT: SQL statement with SQL_ID 33t7fszkr29gy and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
(((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7)))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "33t7fszkr29gy" was executed 1
times and had an average elapsed time of 136 seconds.
RATIONALE: Average CPU used per execution was 138 seconds.
FINDING 3: 15% impact (1008 seconds)
SQL statements with the same text were not shared because of cursor
environment mismatch. This resulted in additional hard parses which were
consuming significant database time.
RECOMMENDATION 1: Application Analysis, 15% benefit (1008 seconds)
ACTION: Look for top reason for cursor environment mismatch in
V$SQL_SHARED_CURSOR.
ADDITIONAL INFORMATION:
Common causes of environment mismatch are session NLS settings, SQL
trace settings and optimizer parameters.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 4: 8.5% impact (570 seconds)
Wait class "User I/O" was consuming significant database time.
NO RECOMMENDATIONS AVAILABLE
ADDITIONAL INFORMATION:
Waits for I/O to temporary tablespaces were not consuming significant
database time.
The throughput of the I/O subsystem was not significantly lower than
expected.
FINDING 5: 5.3% impact (355 seconds)
The SGA was inadequately sized, causing additional I/O or hard parses.
RECOMMENDATION 1: DB Configuration, 3.2% benefit (215 seconds)
ACTION: Increase the size of the SGA by setting the parameter
"sga_target" to 1740 M.
ADDITIONAL INFORMATION:
The value of parameter "sga_target" was "1392 M" during the analysis
period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(8.5% impact [570 seconds])
INFO: Waits for I/O to temporary tablespaces were not consuming
significant database time.
The throughput of the I/O subsystem was not significantly lower
than expected.
FINDING 6: 4.2% impact (281 seconds)
Cursors were getting invalidated due to DDL operations. This resulted in
additional hard parses which were consuming significant database time.
RECOMMENDATION 1: Application Analysis, 4.2% benefit (281 seconds)
ACTION: Investigate appropriateness of DDL operations.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 7: 4% impact (266 seconds)
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
RECOMMENDATION 1: Host Configuration, 4% benefit (266 seconds)
ACTION: Investigate the possibility of improving the performance of I/O
to the online redo log files.
RATIONALE: The average size of writes to the online redo log files was
26 K and the average time per write was 2 milliseconds.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Commit" was consuming significant database time.
(4% impact [266 seconds])
FINDING 8: 2.9% impact (192 seconds)
Soft parsing of SQL statements was consuming significant database time.
RECOMMENDATION 1: Application Analysis, 2.9% benefit (192 seconds)
ACTION: Investigate application logic to keep open the frequently used
cursors. Note that cursors are closed by both cursor close calls and
session disconnects.
RECOMMENDATION 2: DB Configuration, 2.9% benefit (192 seconds)
ACTION: Consider increasing the maximum number of open cursors a session
can have by increasing the value of parameter "open_cursors".
ACTION: Consider increasing the session cursor cache size by increasing
the value of parameter "session_cached_cursors".
RATIONALE: The value of parameter "open_cursors" was "800" during the
analysis period.
RATIONALE: The value of parameter "session_cached_cursors" was "20"
during the analysis period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Contention for latches related to the shared pool was consuming
significant database time. (2% impact [135 seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of database
time.
SYMPTOM: Wait class "Concurrency" was consuming significant database
time. (2.3% impact [154 seconds])
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
Wait class "Application" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.
An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.

user12023161 wrote:
I have upgraded 10.2.0.3.0 to 10.2.0.5.0 and facing same issue. The database is slow in general after upgrade compared to 10.2.0.3.0.Try setting OPTIMIZER_FEATURE_ENABLE parameter to 10.2.0.3.
Refer following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams142.htm

SAP B1 APPLICATION IS RUNNING SLOW IN SERVER AFTER UPGRADE

Hi,
The sap application is running slow in server after upgrading it from 9.0 to 9.1 it's taking 5-10 secs to open a document after clicking it and its taking more time in client system.
what are the steps to be taken so that the application will run without any delay.
Regards,
Karthik B

hi please check bellow thread ,it may help you
Client Machines Logon to SAP Server is Very Slow
update the status
regards
AKR

My iphone got slow on keyboard after upgrade... Any hints ? Tia .

Hi team
my iphone got slow on keyboard after upgrade... Any hints ? Tia .

No, I have not done a restore with no backup but I'll try (when my job will let me some time to spend for myself).
Contacts, music, calendars etc. work fine (I don't have pictures on my iPhone) but everything "feels" slow and intermittent.
I'll let you know about the complete initialization.
cheers
rob

Jerky slow video clips after after importing from Cam Corder

Hi there, my iMovie 06 has been absolutely fine and then I have just imported some video clips using firewire from a camcorder and the audio is fine but the clips are slow and jerky and out of sync - I have just purchased an additional 1GB of memory and added this hoping that it would make a difference (the Apple store seemed to think it would) but it hasn't - and the other movie projects I have which were absolutely fine are also playing back like this - the guy in the apple store tried everything he knew but was baffled - can anyone suggest what is causing this problem and how to rectify it - I have a Powerbook G4 1.5 ghz 12 inch.
Thanks
Jenni

Jenni28,
Are the clips jerky and slow when placed in the timeline? Or also when in the clips pane?
Did you recently upgrade to QuickTime 7.5? Many have reported stuttering/jerking playback after this upgrade.
I, too, just recently upgraded to QT 7.5, and yes, Klaus1, I have the stuttering problem despite following 'most' of your suggestions.
It is similar to what I found in iMovie 5, and in 6 if I put in many audio or video clips. I work around it by importing into clips pane, checking each video clip and cropping there or in timeline. I then add the photos, and do titles and transitions. The stuttering begins after I add several audio clips. I know that the final movie will burn fine, so I just continue with my edits. I export the movie as Full Quality Quicktime and import that into a new iMovie. It plays fine. I add chapter markers and then drag it into iDVD. Burns flawlessly, so I am not too concerned about the jerkiness.
I noticed that it had seemingly resolved with about version 7.2 of QuickTime, but it is now back again. I was in the middle of a couple of iMovies, and I downloaded version 7.5 by accidentally clicking on it. It was nearly finished installing before I discovered what I had done. I decided to work with it.
Klaus, I will apply your recommendations after I finish this and one other movie. Then I will see if it resolves. I don't want to go back to 7.4.5 now.

Choppy playback after upgrading to iTunes 11

I am still on OSX 10.6.8 so I can still use Front Row on my laptop. I just recently upgraded to iTunes 11 and now playback of video will become choppy and sometimes stalls and the sound will also become choppy and unsynchronized with the video. This occurs when playing video on iTunes or Front Row. Has anyone else experienced this and if so, have you come up with a solution?? Thanks in advance.

I was also having this issue on my iMac running OSX 10.6.8 after upgrading to iTunes 11. Clearing my user Library Cache seems to have solved the issue.
In case you're not sure how to do that, open a finder window, hit Cmd-Shift-G to go to a folder, then enter "~/Library/Caches". Select all the contents of the Caches folder, and hit Cmd-Delete. You will be prompted to enter your password in order to delete these files. Restart your machine and empty the bin when you log back in.

Flash 10 and PPC - slow video playback

Have an old PowerBook 12" running 10.5. Since upgrading to
Flash v10 the video playback is slow and sluggish to the point
Flash content is unusable. Tried to download a PPC specific version
but Adobe downloads gave me the Universal Binary once again. I
suspect v10 is buggy and is not supporting "Enable Hardware
Acceleration" on PPC so video is being scaled and processed by
software.
Anyone else having this problem? Anyone able to direct me to
good old v9?

Restarting might help temporarily, but for a more permanent solution you'd need a faster computer processor, a better video card, lots more RAM, and a faster hard drive. The sad truth of the matter is that technology advances so quickly that older computer hardware can't keep up with it. It would actually cost less to buy a new computer than it would to try to upgrade an older model. The iMac CRT's are still useful for many tasks, but they can't be expected to handle present-day multimedia.

Problems with playback after upgrading to 4.4.2.

After upgrading my Apple TV 2nd generation to iOS 4.4.2 a great amount of my HD content won't play.
I get this message: An erorr occurred loading this content. Try again later.
The problem is only associated with HD video, but not every HD video file. All of this content played fined the until upgrading.

I have seen this on mine from time to time. Since the updates, streaming has been messed up.

Dashboard widget with streaming video breaks after upgrade to Mountain Lion

Hi. I recently upgraded from Snow Leopard to Mountain Lion. Under SL, I had an OS X widget that was a web clipping of a streaming mpeg image being produced by a Linksys/Cisco WVC54GCA web camera. When I brought up the dashboard, the OS would start streaming the data from the mpeg filename, which looks like "hostname.com/img/video.mjpeg".
After upgrading to Mountain Lion, I noted that the widget never fully loads, indefinitely displaying a "Loading Clip..." mesasge. After deleting and re-adding, I can still get as far as adding the web clipping to the dashboard at the right dimensions, but there's no content.
Unfortunately the camera unit doesn't provide for the display of HTTP access logs, so I can't see if there's an issue there, but my understanding is that if I can display the image in a Safari browser, it should work just fine in Dashboard too. (I did make sure that, where needed, the username/password for accessing the video are included in the URL.)
I did sniff the network traffic between my system and the camera host, and show that video traffic starts flowing between the two as soon as the widget is brought up. So, it's almost like the widget doesn't know when to stop "loading" and start "displaying," perhaps because the HTTP request is never truly "done."
Can anyone speculate if something may have changed in Mountain Lion affecting the ability of web clipping widgets to display streaming video?
Thanks,
Chris

Hi James
I have exactly the same problem with the same "Loading clip" then blank. I have been trying a lot of stuff to get this working, but haven't had the chance of sniffing the network traffic as you have done. By reading what you said about the traffic seems to be flowing without the picure being displayed makes me even more puzzled by this. I never had a streaming video while I were using Snow Leopard, but I had a still-image, as I also do now in Mountain Lion. I recently began to research for a way to display the video.cgi MIME image that my camera produces, and I've also concluded that this should be an easy task for the dashboard web clip function; the video does display in safari after all.
I suspect that our cameras uses the same built in webserver solution written by a "Steven Wu". Cheap webcameras frequently uses his script with MJPEG (stream of JPEG pictures) to avoid the expensive licenses of using other video codecs.
I read this a bit down at this site: http://channel9.msdn.com/coding4fun/articles/Everyone-Loves-Babies-Webcams-and-M otion-Detection
Have you come any closer in your research?
I have started to think that maybe I have to write a dashboard widget on my own to accomplish this.
trelements

Program Monitor is Black, no video playback after installing new graphics card

I bought a PNY Nvidia Quadro 2000 graphics card a few days ago, and since it's been installed, I've been unable to watch video playback in my program, source or even reference monitor.
Similarly, If I designate one of my monitors soley for video playback, the screen is just black, and as the timecode advances on my timeline I only hear sound.
My project is using "Mercury Playback Engine GPU Acceleration" for Premiere Pro CS6.0.1
I went from using one graphics card to using two graphics cards, and installed a third monitor. I've spent the last few days trying everything I could think of, I even uninstalled and re-installed premiere.
Hardware Specs:
Windows 7 Ultimate (64-bit)
HP Pavilion h8-1230z
AMD-FX8150 3.59Ghz 8 core processesor
16GB RAM
600W PS
EVGA Nvidia GeForce GTX 550Ti
PNY Nvidia Quadro 2000
I am using a PCI x16 for the Quadro 2000
I am using a PCI x1 slot w/x1-x16 adapter for the 550Ti
Could this be the problem?
Additional Information
Vectorscope, All scopes, YC Waveform - Display modes all work.
I downloaded the most recent Nvidia drivers for both of my cards.
I haven't received any error messages or had any problems in After Effects CS6, as video playback is working properly in my other adobe applications.

I am still building a new system, so currently I'm still using a 480. You can read all about my choices and progress here: Adobe Forums: Planning / building a new system. Part 1
There are 11 entries in the Benchmark Results that succesfully use the GTX 680, even though it is not 'supported'. They all use the 'hack'. However, the 680 has been added to the list of supported cards for AE, so it is only a matter of time before the 680 will be added to the list of supported cards for PR. Todd had made that clear. Now, when the 680 is added, it makes sense that the 670 will also be added. My guess is that both will be added in a short while.

Slow video playback in Photoshop Elements 11

Playback of videos directly in Photoshop Elements Organizer is very slow. Video is stuttering.
Playing the same video outside of PSE11 with Windows Media Player is much better. Video plays without any stuttering.
Looks like the internal video player of PSE11 is very poor and provides slow performance.
What can I do do have the same video performance with the PSE11 player as I have with WMP.
I use Windows 7 64 Bit (8 GB RAM) with a Intel Core i3 (2330). This CPU has enough power to playback HD or Full-HD videos without any stuttering!!!
Why can't the internal play of PSE11 Organizer play my videos without stuttering - like WMP 12.0.7601.18150 does?
Regards,
Dodson65

The videos I use are created with different devices.
I have HD videos taken with a Pentax DSLR and I have Full-HD videos taken with a Windows Phone 8 device.
Both playback on my Laptop without any stottering with different software. I checked WMP and VLC. Even when using my Laptop with energy-saving profile these videos can be played without stottering.
When I playback the videos in PSE11 Organizer I don't want to edit them - just playback. So why should the internal player behave different? I agree with you - this might be different when I playback the videos in Premiere Elements 11 (as this is a video editing software). But when using Photoshop Elements 11 I want to be able to playback videos in the same performance as I can do with WMP or VLC. If Photoshop Elements 11 can't do that - why? The organizer of PSE11 is not an editor. It should be able to playback videos the same way (with the same performance) as other players on my laptop.
Can you please explain this sentence: "Have you started a Premiere Elements project yet that uses this video's specs? This will often trigger Premiere Elements to download the necessary components for interpretting the video." Is there anything I can do to improve video playback performance?

Choppy video streaming after upgrading E4200 firmware to ver. 1.0.03

Video streaming was fine until I upgraded the firmware. Is it possible to downgrade the firmware?

You mentioned in your post that you upgraded the latest firmware. So after upgrading the firmware did you reset the router? It is recommended to reset the router after firmware upgrade. Steps to reset the router:
Push the reset button on router for 30 seconds, turn off the router wait for 30 seconds and then power it on. After this process reconfigure the router. Power light should blink when you perform the reset process.
After the process reconfigure the router as per the ISP setup.. Then try to do the following steps:
A] With the help of Cisco Connect Software (if at all you have installed the router with the help of this software)
          1] Open the software and go to the option which says "Router Settings"
          2] Then click on the option which says "Advanced Settings" which will take you to the router's configuration page.
         3] Lower the MTU (Maximum Transmission Unit) from 1500 to 1400 or less (usually found on your router's main/ basic setup page)
         4] Then go to the Wireless tab, keep network mode as mixed,
For Channel Settings of 2.4 GHz you can make Channel Width to 20 MHz only and Channel to 6, 9, 11..
For Channel Settings of 5 GHz you can make Channel Width to 20 MHz only and Channel to 40 or 161...
B] If you haven't installed Cisco Connect then you can log on to the router's user interface using it's default IP address in the browser which is 192.168.1.1 and type in 'admin' as the password leaving the username field blank. This will take you to the router's web interface and then follow steps as mentioned above to make the changes.

Slow video playback in very high resolution X11

Hi everyone. I write this msg for ask your eternal knowledgement.
I have a very huge system (i7 3820 LGA2011, 8Gb quad channel, Gigabyte x79-up5-wifi, AMD HD5870 2Gb Eyefinity 6, etc) running Arch on it. The OS is updated. The Arch config is very minimal, using Fluxbox as WM and VLC and Mplayer to playback videos. The video driver is the latest stable Catalyst (13.4) and so on. I got connected six HD screens seted to a resolution of 1366x768. These screens are managed with xrandr, adjusted for considering the bezel compensation, using xrand --output MONITOR --pos X+BEZELxY+BEZEL.
When i play a video with mplayer (using the gl video driver) the movie shows very well and smooth, but when i pan the video all over de virtual screen (4194x1583 aprox), the movie shows very choppy.
The strange fact is the Conky reports shows me an 5% of CPU usage, so the system performance are not the problem.
The mplayer flags that i use to play this video are plenty, being the threads=4, gl:ati-hack and -root the most important.
If anyone can give me a hint to solve this issue, i would be very grateful.
thx in advance.

The videos I use are created with different devices.
I have HD videos taken with a Pentax DSLR and I have Full-HD videos taken with a Windows Phone 8 device.
Both playback on my Laptop without any stottering with different software. I checked WMP and VLC. Even when using my Laptop with energy-saving profile these videos can be played without stottering.
When I playback the videos in PSE11 Organizer I don't want to edit them - just playback. So why should the internal player behave different? I agree with you - this might be different when I playback the videos in Premiere Elements 11 (as this is a video editing software). But when using Photoshop Elements 11 I want to be able to playback videos in the same performance as I can do with WMP or VLC. If Photoshop Elements 11 can't do that - why? The organizer of PSE11 is not an editor. It should be able to playback videos the same way (with the same performance) as other players on my laptop.
Can you please explain this sentence: "Have you started a Premiere Elements project yet that uses this video's specs? This will often trigger Premiere Elements to download the necessary components for interpretting the video." Is there anything I can do to improve video playback performance?

Slow video playback after upgrading to ati 9200 card

Similar Messages

Maybe you are looking for