Slideshow process extreemly slow
So I recently upgraded to i-life 09. Before the update, to make a slide show in i-photo, I just selected the pics I wanted, made a slideshow, exported it as a QT movie and then I could burn a dvd or drop it into Final Cut. Now, I have selected the pics, created a slideshow file within i-photo, clicked export... and I got the page when I need to select whether I will be using it for i-pod, computer, apple tv, etc... I played around with those options but any which way I did it, I still have the same problem: It takes forever to make a slideshow! I finally finished one this morning after letting it run 6 hours (then I went to bed... not sure how long it actually took). Before that, it had run 3 hours and crashed (got an "unexpected quit" message from i-photo.) I noticed that about half way through the slideshow creating process, the display where it was showing me the pics being made was showing nothing but a black screen. This morning, it had finished the file and was fine. I dropped the file into FCP and it says it will take 10 hours to render!
What am I doing wrong? It used to be so simple! Any ideas? Thanks for your time.
I am using about 110 jpegs (nothing unusual for me). I have 3 gigs of ram and plenty of HD.
Forgot to also mention that I am running the jpegs for 5 seconds each, with Ken Burns effect, no theme, and the file it created was 400m.
Similar Messages
-
SM58 entries processed very slow
Hi Gurus,
currently we are facing problems with TRFC queue entries, during sometimes all entries are struck up in the queue and processed very slowly. For that we have scheduled a TRFCs processing job, but still entries are getting process very slow.
if any one of come across the similar issue, please provide your inputs.
Thanks and Regards,
venkat.A SAP notes search with keywords SM58 and performance could give you a start.
For example:
Note 375566 - Large number of entries in tRFC and qRFC tables
Note 460235 - tRFC/qRFC: Low-speed processing -
TCODE: ME2N is processing very slow
Hi, we have an issue with tcode: ME2N processing very slow. This tcode
was working fast when we went live with SAP. Recently we have noticed
slowness. When users run MEN2N with purchase group 124 to pull PO's, it
takes for ever. I researched and coulnd't find anything specific on
this. Please advise.Hi,
While the end user executing the t-code put a trace against that process id.
In that trace u can definitely find the error.
For example how much time it will take to fetch the data and insert like that,
probably u have to create a secondary index for that particular table or else it is going somewhere in the loop of a program which it is internally using.
Do these things may be u r problem will be solved.
Regards,
Anil -
Enqueue is processing very slow
Hello gurus,
Enqueue is processing very slow, still i can see lot queues are waiting in Enqueue.PLeas esome quickly suggest on this.
Our Production system badly effected by this
regards
VamsiSo, why opening the same thread with 2 different users?
Enqueue is processing very slow and system is alomst hanging -
How can I stop the program from going through all of the text previously put in. It is making the process very slow.
while True:
and just indent everything else under it
Ends when you press ^C.
if you wish to have a way to break out of the loop, say, when you press enter at the VPC number without entering anything, add the following after your vpc input:
if not vpc:
break
which will break out of the while loop and end your program.
Last edited by buttons (2007-12-14 22:03:06) -
my mac has started freezing and suddenly shutting down on me it seems as if every process has slowed down since downloading this last update of 11.1.4, any solutions? Because it shut down in the middle of a test twice now, saying keyboard issue.
What you describe sounds like a hardware issue. Unfortunately, you'll need to get that checked out by Apple. If you have an Apple Store near you, make an appointment with the Genius Bar and take the machine in for evaluation.
-
IDVD 08 Encode slideshow extreemly slow
i am using MacPro 3G 8 core.
iDVD08 to encode 700s photo to a slide show it cost about 3hrs to code that and the cpu around 6-8% usage .
Is it normal ? if yes, another option that i can create a slide show dvd faster ? thanksHere's my only slideshow in iDVD '08. Note may hardware listed below.
Soft Frame theme
Professional Quality encoding
51 min duration
2.90GB
DVD-ROM (images)=1777MB
Slideshows=1113MB
Menus=36MB
Movies (AVI from digicam)=36MB
Slides=548
Transitions=296
Start 6:05 p.m.
Finish 8:30:40
At start of encoding, iDVD '08 estimated 2 hours 52 minutes. -
Bridge CS3 Previews/Slideshow Scaling Too Slow on Powerbook G4 15"
I've been using Photoshop CS3 itself for months and it's plenty fast. Bridge, on the other hand, is unusable for me right now because when I click an 6-megapixel jpeg image, a fuzzy/blotchy preview showed immediately, but it takes a full seven seconds for a high-quality preview to show. The exact same thing occurs in the slideshow mode. Of course, once the high-quality preview has been cached, it shows up instantly, but this is a real issue for newly-viewed files.
Is this a known issue? If so, is there a way to make the high-quality preview reasonably fast, so that there's only a delay of a second or two max?
Graphic Converter is quite snappy for previews and full-screen slideshows on this ~1.6 Ghz G4, but I would prefer to use Bridge for its advanced organizing features and integration with Photoshop.
Thank you for your help,
Cameron>It makes no difference whether your files originated as 10- or 12-megapixel digital camera files or as 120 MB 16-bit Tiff scans, 4,000 images are still 4,000 images!
<br />
<br />Actually, no. How files originate makes
<br />b all
<br /> the difference!
<br />
<br />E.g. a film scan is by definition very slow, so processing, sorting, culling, stacking all occur prior to a few hero images being selected for scanning. Those activities occur manually rather than in software.
<br />
<br />Similarly - again with no disrespect intended - your 4000 images captured over weeks on a slow digicam with a film-centric mindset are
<br />b nothing
<br /> like capturing hundreds or thousands of shots, many of
<br />i dynamic subjects,
<br />during intense DSLR RAW shooting of a day or two.
<br />
<br />E.g. the other day I was alone (meaning no helper to control the feisty new pup) walking my new lab puppy during failing light and decided to shoot a pic for emailing to friends. I would run away from the puppy, turn around and shoot continuous high speed autofocus pix of Ruby as she ran toward me. Even though Ruby can run almost as fast as I can, in 5 minutes of failing light I had shot 50-100 12 MP RAW images that then needed to be keyworded, stacked, stacks reviewed for ranking and culls, and an email generated.
<br />
<br />
<a href="http://www.pixentral.com/show.php?picture=1ybNMDLvrZ84DrWBMZ0a5QE8fKUkY" /></a>
<img alt="Picture hosted by Pixentral" src="http://www.pixentral.com/hosted/1ybNMDLvrZ84DrWBMZ0a5QE8fKUkY_thumb.jpg" border="0" />
<br />Nikon D2x, f/4, 85mm.
<br />
<br />The whole process was easy and fast. With a low end point-and-shoot in failing light I would not have had 50 properly exposed, properly focused naturally lit pix that needed close comparative evaluation. At best one would end up with one or two focused keepers; no fancy software necessary to cull a dozen out-of-focus pix.
<br />
<br />My point is simply that folks who are evolving into DSLR workflows, especially those of dynamic subjects like people (with constantly changing expressions that are well suited to shooting stacks of quick image captures), should beef up their hardware, buy the Aperture tutorial/CD, download the Aperture and/or LR trials and check out a modern workflow. -
When I try to awaken the computer, the screen saver (a changing series of neon-colored rings and dots) does not immediately disappear. It can take a full minute for it to go through different displays before it goes away and is replaced by my desktop. And even after I get my desktop back, it takes forever for applications to launch, and even to type simple words into the google search bar. I type, and then have to wait for the words to appear. Is the appearance of the screen saver and the slow processing a coincidence? If not, what can I do to remove the screen saver (and solve the problem)?
How large is you HD and how much space do you have left?
-
Idoc trfc processing very slow
Hello,
I am troubleshooting slow processing of idocs in an Xi test system.
idocs are being processed at a rate of betwen 40 / 60 per hour so at the current rate there will stil be another 3 days (approx) until the queue is cleared.
In SMQS on the Xi (source) system the specific idoc destination is set-up as follows: -
Clt - 10
Destination - R2RREG100
Type - R
W/o tRFC -
Max.Conn. - 10
Max. Runtime - 60
Status - WAITING
Act.Conn - 5
Host ID - ax2t003a_X2T_43
The RFC connection between the two systems has been tested successfully.
Selecting TRFC Monitor and there are still over 3000 rows similar to the following (was over 7000 when first checked)
Caller - PIAFUSER
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - R2RREG100
Date - 15.12.2011
Time - 12:38:22
Status Text - Transaction recorded
Transaction ID - 8218046C00014EC9DE911C9B
Host - ax2t003a
Tctn
Program - SAPMSSY1
Cln - 10
Rpts - 30
I am told by the application team that processing 7000+ idocs is not a large amount for this system
The Xi (source) system and the R3 destination system have both been restarted to clear memory etc but this has not improved speed of processing.
I presume the problem was caused by trying to process too many idocs at once through the Xi system as mentioned in SAP Note 1548446.
I have read SAP Note 1483757 and checked ST03n last minute load on RFC table in the R3 destination system -
Task Type Name - RFC
#Sequential Read - 4,782,264
T Seq Read - 1,157
Avg Seq Read - 0.2
#Accesses - 13,515,579
T Time - 204
Avg T - 0.0
#Changes - 54,206
T Changes - 63
Avg Changes - 1.2
Calls - 18,352,049
Avg Time - 0.1
#Reads - 1,828,651
#DB Recs- 109,376
#Records - 7,687,467
#Calls - 0
T Time - 0.0
Avg Time - 0.0
Last minute load Table Statistics for the destination system ARFCRSTATE table shows the following :
Table Name - ARFCRSTATE
Records - 1,822
Modifiable - 226
records - 0
Sequential Reads - 1,596
T Access - 1
In accordance with the note I tried setting the following on the detaination system but did not see any improvement in processing speed so have now removed the parameter and scheduling of the report.
1. Set the profile parameter abap/arfcrstate_col_delete to 'X' on the default profile of the destination system.
2. Periodically schedule the RSTRFCEU batch job in intervals of 5 minutes, in the destination system.
Q1 -after setting 'abap/arfcrstate_col_delete' I did not restart the R3 system. Is a restart required for this to take effect?
Q2 - What else should I check to identify why idocs are being processed so slowly ?
Q3 - Is there anything else I could change to speed up processing ?
Many thanks,Many thanks jbagga for your reply.
My issue was resolved by SAP who suggested changing the processing mode for message type in WE20 on the receiver system from "Trigger Immediately" to "Trigger by background program".
With the processing mode set to "Trigger Immedaitely" the sender system calls the receiver, the idoc is stored on the dateabase and the application processing was carried out in the same LUW. As a result of this the send must wait until the application finishes processing the messages before it can anything else.
The processing mode was changed to "Trigger by background program" which decoupled the IDoc transfer from the IDoc application processing, performance immediately improved in the XI (sender) system and cleared the queue.
Regards, -
Adobe Premiere Pro to edit videos export process extremely slow!
Hello,
I use Adobe Premiere Pro to edit videos, and until recently, it’s been working smoothly. The last few times I’ve tried to export, the process has been extremely slow—for example, yesterday the program told me it was going to take 22 hours to export a 527MB video.
My computer has an i7 processor and a decent video card (Radeon HD 7470) so I don’t think that’s the issue, but I can’t see it being the software since I had been successfully exporting videos until recently.
Any suggestions would be greatly appreciated—thanks!Yes
-
Iphoto: "found trace not valid" during export slideshow process
Hello everybody,
I've a problem with IPhoto on my iMac (SW OS X Mountain Lion 10.8.4 (12E55)).
When I try to make a movie (i.e. for my Ipad) starting from a slideshow, after some time the process fails and IPhoto give me back this message: "In the movie I've found a not valid trace".
I've just made all of the following actions:
- repair permissions
- rebuild thumbnail
- repair database
- rebuild database
but unfortunately I haven't solved my problem.
Thanks in advance for your kind help.
Best regards
Alberto from Turin (Italy)There appears to be a bug in QuickTime that prevents exporting a large Slideshow. I would try solitting the slideshow in two and exporting then join it up with iMovie. Or use another app:
Alternatives to iPhoto's slideshow include:
iMovie, on every Mac sold, as is iDVD.
Others, in order of price:
PhotoPresenter $29
PhotoToMovie $49.95
PulpMotion $129
FotoMagico $29 (Home version) ($149 Pro version, which includes PhotoPresenter)
Final Cut Express $199
It's difficult to compare these apps. They have differences in capability - some are driven off templates. some aren't. Some have a wider variety of transitions. Others will have excellent audio controls. It's worth checking them out to see what meets your needs.
However, there is no doubt that Final Cut Express is the most capable app of them all. You get what you pay for.
Regards
TD -
PXI: NI 5600, data lost or stored if the loop time of processing is slow than the acquisition.
I want to know what occurs exactly at the time of L acquisition and the processing data acquired with Ni 5600. When J write my programme of processing of data in Labview, if the loop time of processing of data is slow than the acquisition, I want to know if PXI put the data in a buffer or then the data are lost.
J wait your answer impatiently. You can tell me the documentation were can i read to see the answer.
Anybody can help me.hi abidi,
First, let me tell you how buffered acquisiton works.
If you are using Daq mx for continous acquisition, Labview will autoselect the size of buffer depending on the sampling rate specified.
In sample clock.vi, select sample mode as "continous samples".
Now, Labview will determine the loop speed for reading data that is written into the AI buffer and hence run necssary number of AI read loops to retrieve data from the buffer every second.
this loop speed can also be set by specifying "number of samples per channel" in AI read.vi.
If you leave this value at default ( -1) labview will function as explained above
This can also be set by user ,for example, if your sampling rate is 1000 saples per sec and number of samples per channel is 200, the AI Read functions is performed 5 times in a second.
read this link to get to know about cyclic buffers and continous acquisition.
http://zone.ni.com/devzone/conceptd.nsf/webmain/F2DDCBAD754C687C86256802007B8514
You tell that you are performing some processing on acquired data.
Now, your prgram has to allocate adequate process time for acquiring,retriving data from buffer and then processing it.
the time allocated for processing data depends on the kind of mathematical conversions involved. Nevertheless it is an overhead on the acquisition loop.
this may result in overflow of buffer and data being overwrittien in buffer which results in data loss. An eror message might also pop up to warn that this has happened.
so if your application permits, here's what you can do to avoid this problem
First acquire data and save it on system in ascii or binary fromat.
later retrieve this data file and perform processing /analysis on it.
if you have any further doubts, plz tell.
regards,
Devchander M -
Peformance of one process is slow ( statspack report is attached)
Hi,
My version is 9.2.0.7 (HP-UX Itanium)
we have recently migrated the DB from windows 2003 to Unix (HP-UX Itanium 11.23).
we have one process which usually takes 15 mins before migration, now it is taking 25 mins to complete. I did not change anything at db level. same init.ora parameters. tables and indexes statistiscs are upto to date.
Please guide me, what might be the wrong at instance level. Here I am skipping the sql query portion of statspack report due to security reasons.
this statspack report is taken before running the process and after completion of process.
STATSPACK report for
DB Name DB Id Instance Inst Num Release Cluster Host
UAT 496948094 UAT 1 9.2.0.7.0 NO dbt
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 2 15-Jul-09 10:59:05 11 2.7
End Snap: 3 15-Jul-09 12:42:18 17 4.4
Elapsed: 103.22 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 400M Std Block Size: 8K
Shared Pool Size: 160M Log Buffer: 512K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 44,830.27 435,162.76
Logical reads: 15,223.37 147,771.73
Block changes: 198.12 1,923.15
Physical reads: 47.02 456.37
Physical writes: 7.05 68.45
User calls: 50.01 485.42
Parses: 25.99 252.26
Hard parses: 0.24 2.38
Sorts: 3.40 33.00
Logons: 0.02 0.16
Executes: 34.64 336.27
Transactions: 0.10
% Blocks changed per Read: 1.30 Recursive Call %: 27.05
Rollback per transaction %: 33.70 Rows per Sort: 1532.57
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 100.00
Buffer Hit %: 99.69 In-memory Sort %: 100.00
Library Hit %: 99.38 Soft Parse %: 99.06
Execute to Parse %: 24.98 Latch Hit %: 100.00
Parse CPU to Parse Elapsd %: 48.39 % Non-Parse CPU: 99.53
Shared Pool Statistics Begin End
Memory Usage %: 94.56 94.19
% SQL with executions>1: 74.01 62.51
% Memory for SQL w/exec>1: 52.89 54.29
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
CPU time 895 48.10
db file sequential read 195,597 443 23.83
log file parallel write 1,706 260 13.97
log buffer space 415 122 6.54
control file parallel write 2,074 66 3.53
Wait Events for DB: UAT Instance: UAT Snaps: 2 -3
-> 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
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
db file sequential read 195,597 0 443 2 306.6
log file parallel write 1,706 0 260 152 2.7
log buffer space 415 0 122 293 0.7
control file parallel write 2,074 0 66 32 3.3
log file sync 678 4 51 75 1.1
db file scattered read 6,608 0 21 3 10.4
log file switch completion 9 0 2 208 0.0
SQL*Net more data to client 24,072 0 1 0 37.7
log file single write 18 0 0 19 0.0
db file parallel read 9 0 0 13 0.0
control file sequential read 928 0 0 0 1.5
SQL*Net break/reset to clien 292 0 0 0 0.5
latch free 25 2 0 3 0.0
log file sequential read 18 0 0 2 0.0
LGWR wait for redo copy 37 0 0 0 0.1
direct path read 45 0 0 0 0.1
direct path write 45 0 0 0 0.1
SQL*Net message from client 308,861 0 30,960 100 484.1
SQL*Net more data from clien 26,217 0 3 0 41.1
SQL*Net message to client 308,867 0 0 0 484.1
Background Wait Events for DB: UAT Instance: UAT Snaps: 2 -3
-> ordered by wait time desc, waits desc (idle events last)
Avg
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
log file parallel write 1,706 0 260 152 2.7
control file parallel write 2,074 0 66 32 3.3
log buffer space 10 0 1 149 0.0
db file scattered read 90 0 1 7 0.1
db file sequential read 104 0 1 5 0.2
log file single write 18 0 0 19 0.0
control file sequential read 876 0 0 0 1.4
log file sequential read 18 0 0 2 0.0
latch free 4 2 0 9 0.0
LGWR wait for redo copy 37 0 0 0 0.1
direct path read 45 0 0 0 0.1
direct path write 45 0 0 0 0.1
rdbms ipc message 7,222 5,888 21,416 2965 11.3
pmon timer 2,079 2,079 6,044 2907 3.3
smon timer 21 21 6,002 ###### 0.0
Instance Activity Stats for DB: UAT Instance: UAT Snaps: 2 -3
Statistic Total per Second per Trans
CPU used by this session 89,478 14.5 140.3
CPU used when call started 89,478 14.5 140.3
CR blocks created 148 0.0 0.2
DBWR buffers scanned 158,122 25.5 247.8
DBWR checkpoint buffers written 11,909 1.9 18.7
DBWR checkpoints 3 0.0 0.0
DBWR free buffers found 136,228 22.0 213.5
DBWR lru scans 53 0.0 0.1
DBWR make free requests 53 0.0 0.1
DBWR summed scan depth 158,122 25.5 247.8
DBWR transaction table writes 43 0.0 0.1
DBWR undo block writes 19,283 3.1 30.2
SQL*Net roundtrips to/from client 308,602 49.8 483.7
active txn count during cleanout 6,812 1.1 10.7
background checkpoints completed 3 0.0 0.0
background checkpoints started 3 0.0 0.0
background timeouts 7,204 1.2 11.3
branch node splits 4 0.0 0.0
buffer is not pinned count 35,587,689 5,746.4 55,780.1
buffer is pinned count 202,539,737 32,704.6 317,460.4
bytes received via SQL*Net from c 106,536,068 17,202.7 166,984.4
bytes sent via SQL*Net to client 98,286,059 15,870.5 154,053.4
calls to get snapshot scn: kcmgss 346,517 56.0 543.1
calls to kcmgas 42,563 6.9 66.7
calls to kcmgcs 7,735 1.3 12.1
change write time 12,666 2.1 19.9
cleanout - number of ktugct calls 9,698 1.6 15.2
cleanouts and rollbacks - consist 0 0.0 0.0
cleanouts only - consistent read 1,161 0.2 1.8
cluster key scan block gets 15,789 2.6 24.8
cluster key scans 6,534 1.1 10.2
commit cleanout failures: block l 199 0.0 0.3
commit cleanout failures: buffer 69 0.0 0.1
commit cleanout failures: callbac 0 0.0 0.0
commit cleanouts 40,688 6.6 63.8
commit cleanouts successfully com 40,420 6.5 63.4
commit txn count during cleanout 4,652 0.8 7.3
consistent changes 150 0.0 0.2
consistent gets 93,071,913 15,028.6 145,880.7
consistent gets - examination 1,487,526 240.2 2,331.6
cursor authentications 322 0.1 0.5
data blocks consistent reads - un 51 0.0 0.1
db block changes 1,226,967 198.1 1,923.2
db block gets 1,206,448 194.8 1,891.0
deferred (CURRENT) block cleanout 13,478 2.2 21.1
dirty buffers inspected 9,876 1.6 15.5
enqueue conversions 41 0.0 0.1
enqueue releases 12,783 2.1 20.0
enqueue requests 12,785 2.1 20.0
enqueue waits 0 0.0 0.0
execute count 214,538 34.6 336.3
free buffer inspected 9,879 1.6 15.5
free buffer requested 349,615 56.5 548.0
hot buffers moved to head of LRU 141,298 22.8 221.5
immediate (CR) block cleanout app 1,161 0.2 1.8
immediate (CURRENT) block cleanou 23,894 3.9 37.5
Instance Activity Stats for DB: UAT Instance: UAT Snaps: 2 -3
Statistic Total per Second per Trans
index fast full scans (full) 19 0.0 0.0
index fetch by key 671,512 108.4 1,052.5
index scans kdiixs1 56,328,309 9,095.5 88,288.9
leaf node 90-10 splits 16 0.0 0.0
leaf node splits 2,187 0.4 3.4
logons cumulative 105 0.0 0.2
messages received 1,653 0.3 2.6
messages sent 1,653 0.3 2.6
no buffer to keep pinned count 0 0.0 0.0
no work - consistent read gets 35,118,594 5,670.7 55,044.8
opened cursors cumulative 4,036 0.7 6.3
parse count (failures) 43 0.0 0.1
parse count (hard) 1,516 0.2 2.4
parse count (total) 160,939 26.0 252.3
parse time cpu 421 0.1 0.7
parse time elapsed 870 0.1 1.4
physical reads 291,165 47.0 456.4
physical reads direct 45 0.0 0.1
physical writes 43,672 7.1 68.5
physical writes direct 45 0.0 0.1
physical writes non checkpoint 41,379 6.7 64.9
pinned buffers inspected 3 0.0 0.0
prefetched blocks 88,896 14.4 139.3
prefetched blocks aged out before 22 0.0 0.0
process last non-idle time 75,777 12.2 118.8
recursive calls 114,829 18.5 180.0
recursive cpu usage 11,704 1.9 18.3
redo blocks written 275,521 44.5 431.9
redo buffer allocation retries 419 0.1 0.7
redo entries 623,735 100.7 977.6
redo log space requests 10 0.0 0.0
redo log space wait time 192 0.0 0.3
redo ordering marks 3 0.0 0.0
redo size 277,633,840 44,830.3 435,162.8
redo synch time 5,185 0.8 8.1
redo synch writes 675 0.1 1.1
redo wastage 818,952 132.2 1,283.6
redo write time 26,562 4.3 41.6
redo writes 1,705 0.3 2.7
rollback changes - undo records a 395 0.1 0.6
rollbacks only - consistent read 49 0.0 0.1
rows fetched via callback 553,910 89.4 868.2
session connect time 74,797 12.1 117.2
session logical reads 94,278,361 15,223.4 147,771.7
session pga memory 2,243,808 362.3 3,516.9
session pga memory max 1,790,880 289.2 2,807.0
session uga memory 2,096,104 338.5 3,285.4
session uga memory max 32,637,856 5,270.1 51,156.5
shared hash latch upgrades - no w 56,430,882 9,112.0 88,449.7
sorts (memory) 21,055 3.4 33.0
sorts (rows) 32,268,330 5,210.5 50,577.3
summed dirty queue length 53,238 8.6 83.5
switch current to new buffer 37,071 6.0 58.1
table fetch by rowid 90,385,043 14,594.7 141,669.4
table fetch continued row 104,336 16.9 163.5
table scan blocks gotten 376,181 60.7 589.6
Instance Activity Stats for DB: UAT Instance: UAT Snaps: 2 -3
Statistic Total per Second per Trans
table scan rows gotten 5,103,693 824.1 7,999.5
table scans (long tables) 97 0.0 0.2
table scans (short tables) 53,485 8.6 83.8
transaction rollbacks 247 0.0 0.4
user calls 309,698 50.0 485.4
user commits 423 0.1 0.7
user rollbacks 215 0.0 0.3
workarea executions - opt 37,753 6.1 59.2
write clones created in foregroun 718 0.1 1.1
Tablespace IO Stats for DB: UAT Instance: UAT Snaps: 2 -3
->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)
USERS
200,144 32 2.3 1.4 22,576 4 0 0.0
UNDOTBS1
38 0 9.5 1.0 19,348 3 0 0.0
SYSTEM
2,016 0 4.7 1.5 505 0 0 0.0
TOOLS
14 0 9.3 1.3 1,237 0 0 0.0
IMAGES
3 0 6.7 1.0 3 0 0 0.0
INDX
3 0 6.7 1.0 3 0 0 0.0
Buffer Pool Statistics for DB: UAT Instance: UAT Snaps: 2 -3
-> Standard block size Pools D: default, K: keep, R: recycle
-> Default Pools for other block sizes: 2k, 4k, 8k, 16k, 32k
Free Write Buffer
Number of Cache Buffer Physical Physical Buffer Complete Busy
P Buffers Hit % Gets Reads Writes Waits Waits Waits
D 49,625 99.7 94,278,286 291,074 43,627 0 0 0
Instance Recovery Stats for DB: UAT Instance: UAT Snaps: 2 -3
-> B: Begin snapshot, E: End snapshot
Targt Estd Log File Log Ckpt Log Ckpt
MTTR MTTR Recovery Actual Target Size Timeout Interval
(s) (s) Estd IOs Redo Blks Redo Blks Redo Blks Redo Blks Redo Blks
B 38 9 2311 13283 13021 92160 13021
E 38 7 899 4041 3767 92160 3767
Buffer Pool Advisory for DB: UAT Instance: UAT End Snap: 3
-> Only rows with estimated physical reads >0 are displayed
-> ordered by Block Size, Buffers For Estimate (default block size first)
Size for Size Buffers for Est Physical Estimated
P Estimate (M) Factr Estimate Read Factor Physical Reads
D 32 .1 3,970 2.94 2,922,389
D 64 .2 7,940 2.54 2,524,222
D 96 .2 11,910 2.38 2,365,570
D 128 .3 15,880 2.27 2,262,338
D 160 .4 19,850 2.19 2,183,287
D 192 .5 23,820 1.97 1,962,758
D 224 .6 27,790 1.30 1,293,415
D 256 .6 31,760 1.21 1,203,737
D 288 .7 35,730 1.10 1,096,115
D 320 .8 39,700 1.06 1,056,077
D 352 .9 43,670 1.04 1,036,708
D 384 1.0 47,640 1.02 1,012,912
D 400 1.0 49,625 1.00 995,426
D 416 1.0 51,610 0.99 982,641
D 448 1.1 55,580 0.97 966,874
D 480 1.2 59,550 0.89 890,749
D 512 1.3 63,520 0.88 879,062
D 544 1.4 67,490 0.87 864,539
D 576 1.4 71,460 0.80 800,284
D 608 1.5 75,430 0.76 756,222
D 640 1.6 79,400 0.75 749,473
PGA Aggr Target Stats for DB: UAT Instance: UAT Snaps: 2 -3
-> B: Begin snap E: End snap (rows dentified with B or E contain data
which is absolute i.e. not diffed over the interval)
-> PGA cache hit % - percentage of W/A (WorkArea) data processed only in-memory
-> Auto PGA Target - actual workarea memory target
-> W/A PGA Used - amount of memory used for all Workareas (manual + auto)
-> %PGA W/A Mem - percentage of PGA memory allocated to workareas
-> %Auto W/A Mem - percentage of workarea memory controlled by Auto Mem Mgmt
-> %Man W/A Mem - percentage of workarea memory under manual control
PGA Cache Hit % W/A MB Processed Extra W/A MB Read/Written
100.0 851 0
%PGA %Auto %Man
PGA Aggr Auto PGA PGA Mem W/A PGA W/A W/A W/A Global Mem
Target(M) Target(M) Alloc(M) Used(M) Mem Mem Mem Bound(K)
B 320 282 12.6 0.0 .0 .0 .0 16,384
E 320 281 15.3 0.0 .0 .0 .0 16,384
PGA Aggr Target Histogram for DB: UAT Instance: UAT Snaps: 2 -3
-> Opt Executions are purely in-memory operations
Low High
Opt Opt Total Execs Opt Execs 1-Pass Execs M-Pass Execs
8K 16K 37,010 37,010 0 0
16K 32K 70 70 0 0
32K 64K 11 11 0 0
64K 128K 34 34 0 0
128K 256K 9 9 0 0
256K 512K 54 54 0 0
512K 1024K 536 536 0 0
1M 2M 7 7 0 0
2M 4M 24 24 0 0
PGA Memory Advisory for DB: UAT Instance: UAT End Snap: 3
-> When using Auto Memory Mgmt, minly choose a pga_aggregate_target value
where Estd PGA Overalloc Count is 0
Estd Extra Estd PGA Estd PGA
PGA Target Size W/A MB W/A MB Read/ Cache Overalloc
Est (MB) Factr Processed Written to Disk Hit % Count
40 0.1 3,269.7 98.2 97.0 0
80 0.3 3,269.7 9.6 100.0 0
160 0.5 3,269.7 9.6 100.0 0
240 0.8 3,269.7 0.0 100.0 0
320 1.0 3,269.7 0.0 100.0 0
384 1.2 3,269.7 0.0 100.0 0
448 1.4 3,269.7 0.0 100.0 0
512 1.6 3,269.7 0.0 100.0 0
576 1.8 3,269.7 0.0 100.0 0
640 2.0 3,269.7 0.0 100.0 0
960 3.0 3,269.7 0.0 100.0 0
1,280 4.0 3,269.7 0.0 100.0 0
1,920 6.0 3,269.7 0.0 100.0 0
2,560 8.0 3,269.7 0.0 100.0 0
-------------------------------------------------------------Rollback Segment Stats for DB: UAT Instance: UAT Snaps: 2 -3
->A high value for "Pct Waits" suggests more rollback segments may be required
->RBS stats may not be accurate between begin and end snaps when using Auto Undo
managment, as RBS may be dynamically created and dropped as needed
Trans Table Pct Undo Bytes
RBS No Gets Waits Written Wraps Shrinks Extends
0 22.0 0.00 0 0 0 0
1 650.0 0.00 1,868,300 0 0 0
2 1,987.0 0.00 4,613,768 9 0 7
3 6,070.0 0.00 24,237,494 37 0 36
4 223.0 0.00 418,942 3 0 1
5 621.0 0.00 1,749,086 11 0 11
6 8,313.0 0.00 48,389,590 54 0 52
7 7,248.0 0.00 14,477,004 19 0 17
8 1,883.0 0.00 12,332,646 14 0 12
9 2,729.0 0.00 17,820,450 19 0 19
10 1,009.0 0.00 2,857,150 5 0 3
Rollback Segment Storage for DB: UAT Instance: UAT Snaps: 2 -3
->Opt Size should be larger than Avg Active
RBS No Segment Size Avg Active Opt Size Maximum Size
0 450,560 0 450,560
1 8,511,488 6,553 8,511,488
2 8,511,488 4,592,363 18,997,248
3 29,351,936 14,755,792 29,483,008
4 2,220,032 105,188 2,220,032
5 3,137,536 3,416,104 54,648,832
6 55,697,408 21,595,184 55,697,408
7 26,337,280 9,221,107 26,337,280
8 13,754,368 5,142,374 13,754,368
9 22,011,904 10,220,526 22,011,904
10 4,317,184 3,810,892 13,754,368
Undo Segment Summary for DB: UAT Instance: UAT Snaps: 2 -3
-> Undo segment block stats:
-> uS - unexpired Stolen, uR - unexpired Released, uU - unexpired reUsed
-> eS - expired Stolen, eR - expired Released, eU - expired reUsed
Undo Undo Num Max Qry Max Tx Snapshot Out of uS/uR/uU/
TS# Blocks Trans Len (s) Concurcy Too Old Space eS/eR/eU
1 19,305 109,683 648 3 0 0 0/0/0/0/0/0
Undo Segment Stats for DB: UAT Instance: UAT Snaps: 2 -3
-> ordered by Time desc
Undo Num Max Qry Max Tx Snap Out of uS/uR/uU/
End Time Blocks Trans Len (s) Concy Too Old Space eS/eR/eU
15-Jul 12:32 10 13,451 3 2 0 0 0/0/0/0/0/0
15-Jul 12:22 87 13,384 6 1 0 0 0/0/0/0/0/0
15-Jul 12:12 3,746 13,229 91 1 0 0 0/0/0/0/0/0
15-Jul 12:02 8,949 13,127 648 1 0 0 0/0/0/0/0/0
15-Jul 11:52 1,496 10,476 24 1 0 0 0/0/0/0/0/0
15-Jul 11:42 3,895 10,441 6 1 0 0 0/0/0/0/0/0
15-Jul 11:32 531 9,155 1 3 0 0 0/0/0/0/0/0
15-Jul 11:22 0 8,837 3 0 0 0 0/0/0/0/0/0
15-Jul 11:12 4 8,817 3 1 0 0 0/0/0/0/0/0
15-Jul 11:02 587 8,766 2 2 0 0 0/0/0/0/0/0
Latch Activity for DB: UAT Instance: UAT Snaps: 2 -3
->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
willing-to-wait latch get requests
->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
->"Pct Misses" for both should be very close to 0.0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
Consistent RBA 1,708 0.0 0 0
FIB s.o chain latch 40 0.0 0 0
FOB s.o list latch 467 0.0 0 0
SQL memory manager latch 1 0.0 0 2,038 0.0
SQL memory manager worka 174,015 0.0 0 0
active checkpoint queue 2,081 0.0 0 0
archive control 1 0.0 0 0
cache buffer handles 162,618 0.0 0 0
cache buffers chains 190,111,507 0.0 0.2 0 426,778 0.0
cache buffers lru chain 425,142 0.0 0.2 0 65,895 0.0
channel handle pool latc 202 0.0 0 0
channel operations paren 4,405 0.0 0 0
checkpoint queue latch 228,932 0.0 0.0 0 41,321 0.0
child cursor hash table 18,320 0.0 0 0
commit callback allocati 4 0.0 0 0
dml lock allocation 2,482 0.0 0 0
dummy allocation 204 0.0 0 0
enqueue hash chains 25,615 0.0 0 0
enqueues 15,416 0.0 0 0
event group latch 104 0.0 0 0
hash table column usage 410 0.0 0 191,319 0.0
internal temp table obje 1,048 0.0 0 0
job_queue_processes para 103 0.0 0 0
ktm global data 21 0.0 0 0
lgwr LWN SCN 3,215 0.0 0.0 0 0
library cache 1,657,451 0.0 0.0 0 1,479 0.1
library cache load lock 1,126 0.0 0 0
library cache pin 1,112,420 0.0 0.0 0 0
library cache pin alloca 670,952 0.0 0.0 0 0
list of block allocation 2,748 0.0 0 0
loader state object free 36 0.0 0 0
longop free list parent 1 0.0 0 1 0.0
messages 19,427 0.0 0 0
mostly latch-free SCN 3,229 0.3 0.0 0 0
multiblock read objects 15,022 0.0 0 0
ncodef allocation latch 99 0.0 0 0
object stats modificatio 28 0.0 0 0
post/wait queue 1,810 0.0 0 1,102 0.0
process allocation 202 0.0 0 104 0.0
process group creation 202 0.0 0 0
redo allocation 629,175 0.0 0.0 0 0
redo copy 0 0 623,865 0.0
redo writing 11,487 0.0 0 0
row cache enqueue latch 197,626 0.0 0 0
row cache objects 201,089 0.0 0 642 0.0
sequence cache 348 0.0 0 0
session allocation 3,634 0.1 0.0 0 0
session idle bit 621,031 0.0 0 0
session switching 99 0.0 0 0
session timer 2,079 0.0 0 0
Latch Activity for DB: UAT Instance: UAT Snaps: 2 -3
->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
willing-to-wait latch get requests
->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
->"Pct Misses" for both should be very close to 0.0
Pct Avg Wait Pct
Get Get Slps Time NoWait NoWait
Latch Requests Miss /Miss (s) Requests Miss
shared pool 786,331 0.0 0.1 0 0
sim partition latch 0 0 193 0.0
simulator hash latch 5,885,552 0.0 0 0
simulator lru latch 12,981 0.0 0 66,129 0.0
sort extent pool 120 0.0 0 0
transaction allocation 249 0.0 0 0
transaction branch alloc 99 0.0 0 0
undo global data 27,867 0.0 0 0
user lock 396 0.0 0 0
Latch Sleep breakdown for DB: UAT Instance: UAT Snaps: 2 -3
-> ordered by misses desc
Get Spin &
Latch Name Requests Misses Sleeps Sleeps 1->4
cache buffers lru chain 425,142 82 15 67/15/0/0/0
library cache 1,657,451 76 3 73/3/0/0/0
shared pool 786,331 37 2 35/2/0/0/0
redo allocation 629,175 31 1 30/1/0/0/0
cache buffers chains 190,111,507 21 4 19/0/2/0/0
Latch Miss Sources for DB: UAT Instance: UAT Snaps: 2 -3
-> only latches with sleeps are shown
-> ordered by name, sleeps desc
NoWait Waiter
Latch Name Where Misses Sleeps Sleeps
cache buffers chains kcbget: pin buffer 0 2 0
cache buffers chains kcbgtcr: fast path 0 2 0
cache buffers lru chain kcbbiop: lru scan 2 12 0
cache buffers lru chain kcbbwlru 0 2 0
cache buffers lru chain kcbbxsv: move to being wri 0 1 0
library cache kgllkdl: child: cleanup 0 1 0
library cache kglpin: child: heap proces 0 1 0
library cache kglpndl: child: before pro 0 1 0
redo allocation kcrfwi: more space 0 1 0
shared pool kghalo 0 2 0
------------------------------------------------------------- -
Kernel_ rask process is slowing Macbook Pro Late 2011 down dramatically
I have Macbook Pro Late 2011 8GB ram, 500 SSD. Once I upgrade to Yosemite I noticed that once I unplugged the power supply"wall adapted" kernel_task process would use up 100% of CPU. Can someone assist me?
The battery needs to be replaced, or there is some other hardware issue.
Maybe you are looking for
-
Using non-XML content in a report key
I have the desire within a proxy service to log a particular key/value pair in a report log where the key value is not within any XML document I have. Basically, during the logic within the proxy service, the service has come up with a specific resul
-
How to retrieve sales order line type
Hello, Maybe I found a workaround for the previous issue but I faced a new problem (matrix of form 139). I tried to read the matrix column 257 but it's always blank even if the row is a text row (of type = T). I need to exclude this type of line in a
-
Hello, Curretly I met another challenge about the CWgraph3D control. I want to show a background image on a fixed ranges/axes area of the CWgraph3D control in the XY view (or any of the other two projection, does not matter). What I mean is, I have m
-
Iphoto won't open after laptop powered down (ran out of batteries)
I was transferring some photos from iphoto to facebook when my macbook pro ran out of charge. When I plugged it back on, iphoto would not open. Blank with spinning rainbow disc. I had to force quit several times. How do I back up my pics? Are they lo
-
I need to transfer my old ipad to my new ipad thro windows cos the files are to large for icloud?
i need to transfer my old ipad to my new ipad thro windows cos the files are to large for icloud? how do i do that? am very green at these matters!!