Slow to wake after OS X 10.4.5
After installing OS X 10.4.5, my old G4/400/AGP is slow to wake, taking
35 seconds before coming to life. Repairing permissions, repairing
disk, and system check all show nothing out of the ordinary. Activity
monitor will function during this period, but doesn't indicate anything
abnormal in the way of disk activity, CPU, or memory during the 35
seconds. This delay happens whether there are applications running or
not. I trashed the powermanagement.plist, thinking it might be
corrupted, but that didn't help.
My iBook G4 also has OS 10.4.5, similar applications, in a similar
environment, but wakes up in less than 5 seconds.
What would OS X 10.4.5 be doing on a G4/400 after wakeup that locks the
system for 35 seconds? Is there a way to spy on the system activity
during that 35 seconds and hopefully point me to the culprit?
G4/400 AGP Mac OS X (10.4.5)
You may be on to something. The G4/400 took an angonizing 3 minutes to restart. It hung for 2 minutes on the gray screen with the spinning clock face.
I don't have any benchmarks, but I recall a 60 second startup was the norm before OS X 10.4.5. iBook G4, which doesn't have the waking problem, starts up in 45 seconds.
G4/400 AGP Mac OS X (10.4.5)
Similar Messages
-
Why is my Macbook Pro slow to wake after sleep?
Why is my Macbook Pro slow to wake after sleep?
I am having the same issue. I hook it up to the charger in the evening and close the lid. When I go to use it the next time it takes a good 30 seconds or so to wake up. The screen shows the log in screen but typing doesn't work and the cursor is frozen. Sometimes it will even give the rainbow wheel for the cursor, so it seem like it is processing whatever to get going. I also notice that my battery won't be fully charged at anywhere from 95%-99% after being charged a full evening. What can I do to change whatever is happening because it is pretty crappy to charge it all night expecting to have a full battery for the next use, plus the issue of having to sit there waiting for it to boot every time.
-
Droid razr m is slow to wake after update
I updated my razr m two days ago, and now my phone has been very slow to wake, sometimes over a minute. This happens even when my alarm sounds and it started more than 24 hours after the update.
Let's see what's going on with your phones goldeneyes. Do you mean from being powered off, to on? Or do you mean to get back to a normal screen takes so long? Please elaborate so we can better understand and assist.
Thank you,
VanessaS_VZW
Follow us on Twitter @VZWSupport -
Slow to wake after "sleeping".
Recently when my mac "sleeps" the monitor is hard to awaken. The screen stays dark and clicking a key or hitting the space bar doesn't bring a quick response as it once did. It takes a minute or two before it wakes. This is a new computer only 4 months old. What could be causing this?
Some users have reported solving this problem by resetting the NVRAM (PRAM.) One user reports long delays in waking from sleep after enabling FileVault. I can't reproduce that experience, but if applicable, you could try disabling FileVault.
If you've installed something called "iCleanMemory," or any other third-party software that is supposed to "clean" or "free up" memory, remove it according to the developer's instructions after backing up all data. Reboot and test. If there's no change, continue.
Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test. -
My mighty mouse (not wireless) is now very slow to wake up after my Mac awakes from sleep. It may take 30 seconds for the mouse to be recognized after my Mac wakes up, and, of course, the Mac will not awake with mouse movement or click.
I tried zapping the PRAM, but this did not help.
Message was edited by: Fred L JohnsonThis is NOT a wireless mouse.
Sorry, Fred. I completely skipped by your parenthetical notation to that effect.
Barry
P.S. The USB port suggestion from Carolyn is worth trying. If you want to try to locate the cause of the problem, take a look at the console and system logs to see if anything is going on at system wake. There is no software setting that I am aware of that would cause what you describe. -
MacBook Pro 13 " going slower in performance after Installing LION OSX
Hey Guys ,
I had noticed some problems in my MacBook Pro 13" which I bought in the MID of 2011 ( i5 processor ) , I had purchased and installed LION OSX and observed after installing that my Backlite ( Keyboard ) dont get on when I start up at the LOG IN , which used to work in SNOW LEOPARD .
Booting takes SO SO SO long as when comapared with the previous OS .
Heating Problem is also a must to mention .
If you guys know how to reduce these problems please help me out !
Thank You .I'm curious if you ever found a solution for this issue. I recently purchased the SanDisk Extreme II 480GB, replacing my OWC Extreme Pro 240GB. The OWC never experienced the "slow to wake" issue whereas the SanDisk drive does, consistently. To make sure I'm having the same symptoms, this is what happens to me: Put the mac to sleep (either manually or letting it do it on its own, waiting for the led to pulse showing that it is asleep), then wake it up (press a key on the keyboard), the logon screen shows almost immediately but as soon as I try to type the pinwheel/beach ball shows up, I wait between 20 and 30 seconds and then I'm able to type and all is well.
I contataced SanDisk and their support was horrible. They simply told me "contact MAC for this issue" (no joke, not "contact Apple" but "contact MAC", in all caps). I explained that it works fine with the OWC drive just not the SanDisk. They replied with another article showing that all macs have trouble waking from sleep (not true). I replied again indicating that I've never had this issue with any of my 3rd party drives, only this SanDisk. Then the replied simply stating that all mac's have issues with 3rd party hard drives when waking from sleep. At this point I threw a fit and yelled at my screen, even though it wasn't my screens fault.
In any case, their support has not been willing to do any actual troubleshooting. I'd love to return it and I might have to - but as you stated, it's annoying to have this issue but the performance is fine the rest of the time.
Thanks for any input you have.
Bryan -
Since updating to Mavericks, my imac is very slow to wake from sleep. Is there a workaround or is it a case of waiting for an update?
Mine does not wake at all,
After installing mavericks, the iMac will not wake from sleep properly (at all)
I think I waited about 5 minutes at one time, but it did not wake!! -
I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro.
I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro (8 Core 2.93GHz). When I run the Mac Pro with 2 x 2Gb RAM it takes 4 seconds before the gray screen, chime and spinning wheel appear.However when I expand the RAM to 20GB the grey screen and chimes appear after a long 20+ second black screen.
The RAM modules are paored 2 x 4GB Crucial CT51272BA1339.M18FMR and 6 x 2GB SAMSUNG M391B5673FH0-CH9, all DDR3 ECC.
Reading articles on the internet, I thought it may be damaged RAM modules, but I have completed memtest and all are okay. I have tried changing the pairs around and if I use any paired 2 modules the Mac Pro starts normally, only when I try running more than 2 modules the delayed start up happens. (black screen 20 Seconds)
I also have tried PRAM and SMU resets after changing the RAM setups, and the issues always occurs when I have more than 2 modules. As you can see I have 6 SAMSUNG modules and even with identical modules the issue happens, when increasing the RAM to more than 2 modules.
The Mac Pro runs fine after the start up screen and can see all the modules, but has anyone else come across this issue, or have any ideas as to why my Mac Pro is taking 20 seconds to start up with 20 GB RAM?Hi there. Thanks for your comments.
I have tried all the different combinations of RAM setup, and as stated in my initial topic, the Mac Pro boot up time only slows when I have more that 2 modules. Where I place these does not seem to make a difference.
I have taken the Mac Pro to an Apple Reseller technician yesterday and they where not able to find any RAM errors. Apparently the boot up time is within Apple's acceptable parameters for this set up.
Could anyone that is running a Mac Pro 2009 with more that 4 modules of RAM, please let me know if the boot up time is normal. ( the time it takes from pressing the power button to seeing the gray screen around 16 - 20 seconds)
Or is anyone else having the same issues?
thanks for your responce -
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 -
Mac Book pro slow to wake from sleep
Hi , Sometimes when I leave my mac book pro and it goes to sleep (screen goes black when lid open) it takes a while to wake from sleep again - sometimes up to 30-40 seconds? This seems very odd for an expensive machine that is around 6 months old and something that never used to happen with my old powerbook G4. It doesn't happen all the time but regularly. Should I be worried? Any help greatly appreciated!
I'm curious if you ever found a solution for this issue. I recently purchased the SanDisk Extreme II 480GB, replacing my OWC Extreme Pro 240GB. The OWC never experienced the "slow to wake" issue whereas the SanDisk drive does, consistently. To make sure I'm having the same symptoms, this is what happens to me: Put the mac to sleep (either manually or letting it do it on its own, waiting for the led to pulse showing that it is asleep), then wake it up (press a key on the keyboard), the logon screen shows almost immediately but as soon as I try to type the pinwheel/beach ball shows up, I wait between 20 and 30 seconds and then I'm able to type and all is well.
I contataced SanDisk and their support was horrible. They simply told me "contact MAC for this issue" (no joke, not "contact Apple" but "contact MAC", in all caps). I explained that it works fine with the OWC drive just not the SanDisk. They replied with another article showing that all macs have trouble waking from sleep (not true). I replied again indicating that I've never had this issue with any of my 3rd party drives, only this SanDisk. Then the replied simply stating that all mac's have issues with 3rd party hard drives when waking from sleep. At this point I threw a fit and yelled at my screen, even though it wasn't my screens fault.
In any case, their support has not been willing to do any actual troubleshooting. I'd love to return it and I might have to - but as you stated, it's annoying to have this issue but the performance is fine the rest of the time.
Thanks for any input you have.
Bryan -
My iPhone has been like this for two months (see link for video). Its extremely slow to wake (this video shows it waking faster than it usually does) and it has a powerpoint-esque windowshade animation looking animation when it wakes (visible in video). The longer the phone has been on and used for, the slower it is to wake. Any ideas on what I can do to fix this? I've already tried doing two DFU restores and setting it up as a new iPhone, but that didn't fix it. Its not jail broken and it is running the latest version of iOS. Its a CDMA White iPhone 4 16gb.
http://www.youtube.com/watch?v=41O52...ature=youtu.behttp://www.youtube.com/watch?v=41O52VRUvAc
Video should now work. Please help me. -
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 Bhi please check bellow thread ,it may help you
Client Machines Logon to SAP Server is Very Slow
update the status
regards
AKR -
Adobe InDesign CC slow to initialise after machine restart
I am finding that InDesign CC is extremely slow to launch after I restart my iMac (takes around 2 minutes). Once it has been launched once it then launches far more quickly (around 20sec). If I log out then back in it still only takes around 20secs to launch. But as soon as I restart my machine the first launch takes around 2 minutes again.
I am assuming that InDesign is copying items to a temporary location (outside of my user space) that is getting reset at restart. My question is, is this a known behaviour, if so can it be got around (something like identifying the temporary files and copying them to the correct temporary location at login)?
System Details
iMac 3.06Ghz, 8Gb RAM, MacOS 10.9.4
Adobe InDesign CC (10.1.0.71)
Any input would be appreciated.Thanks Mylenium
Mac Pro mid 2010, 2 x 2.4 Ghz Quad-Core Intel Xeon
New Mac Pro 2014, 3.7 Ghz Quad-Core Intel Xeon ES
iMac 2014, 3.4 Ghz Intel Core i5
OS X 10.9.2, OS X 10.9.3, OS X 10.8.5
We were not able to get any crash reports - that option not available; the spinning wheel was coming on and off, but nothing would happen and nothing could be done, but re-start machines.
Have cleared prefs files since, this a few times. Based on suggestions found from others having the same problems.
After clearing prefs files, worked awhile , then the same happened.
Hope this helps. -
Ethernet Connection Slow to Wake Up Since 10.6.5 Update
My iMac10,1 (late 2009) is connected to the internet via ethernet using a Netgear WR614v7 and since upgrading to OS X 10.6.5 last Wednesday waking from sleep and connecting to the internet has become an issue. Not always, but often it won't connect. Eventually, after 2 or 3 minutes it seems to sort itself out and connects.
If I connect via wifi I have no problems, although I'd prefer to use a wired connection.
I used the combo to update and took the normal precautions of checking the drive beforehand and fixing permissions, etc. I've done an SMC and PRAM reset.
Anyone else experiencing this? Any knowledge gratefully received.My mini is DEFINITELY having internet connect issues since upgrading to 10.6.5. Always used wifi for convenience of no cable. However wifi gradually degrades or won't connect to the point it's unusable. I know it's not my wifi router because a Windows 7 laptop connecting the same way is smoking (as painful as that is to admit). I've gone hard wired for now because it's the only way I can use the mini and be productive until I find a resolution. However, even hard wired, it takes a few minutes when I wake after the machine has been in sleep mode before hard wired will connect. I've disabled wifi, created a new network connection where only ethernet is active. Computer sits in a 'cable disconnected' mode for 2 - 3 minutes before finally going online. Something happened in 10.6.5. I've reset PRAM, SMU, and anything else I can find to reset to no avail. Very frustrating.
-
Slow Booting time after installing MacBook Pro EFI Firmware Update 2.0 on 13 Inches Mac 2010 model
I'm experiencing a slow boot time after my computer installed a MacBook Pro EFI Firmware Update 2.0 itself on 13 Inches 2010 model, how to downgrade or fix it?
My computer is starting 2 times slower then it should be, why Apple done this to me?
Please help who really know somthing about Macs.I have the same problem, especially when I open my laptop from sleep. It takes at least 2 minutes for the computer Internet connection to work.
Never had that problem prior to the last firmware update 2.7.
Is there a way to revert back to 2.6?
Maybe you are looking for
-
How do I do a clean install, and keep mail accounts?
A little background: We have several Macs, and several email accounts. We're buying new machines and on some would like to mostly start over, using the App Store to install programs as each machine requires, cutting out a lot of the disk loading. The
-
Mac Pro not sending video to my DV Camera
Hi, I have been editing on a PowerMac G5 using FCP 5.1.4 and outputting to tape on my Sony TRV900 MiniDV camera with no problems for over a year. I have recently bought a Mac Pro, and although I can get footage OFF to camera, the Mac Pro appears not
-
Best WMA to MP3 batch converter for MacBook Pro
Half of the music that I've collected over the years, and now transferred onto my new MacBook Pro, is in the WMA format. I am looking for a program that can batch convert ALL of these files to MP3, putting the MP3s in the same folders as the WMA file
-
Using midi drums and Logic sounds
Hi guys I have been looking at the different softwares to use with my Alesis DM10 and Logic Pro X using the USB as when I currently record it just catches the midi notes and no sounds I have seen BFD, NI Drums and the various others but they cost mon
-
Windows 8 not active after factory reset
I bought this laptop a year ago in US, with windows 8 and was upgradable to 8.1. I upgraded and was using 8.1, until 2 days before when system crashed. I was not able to perform a system restore, therefore did a factory reset. Now when the system boo