Poor System Performance with Aperture 3

I am using a MBP (3,1) 15", 4 GB Ram, 2.6 ghz processor with Snow Leopard 10.6.2
After I run an import of photos, the entire system very nearly comes to a complete halt. EVERYTHING lags while Aperture does its post import processing, and then for 5-10 minutes after it says it has completed.
I am having the same result on my dual quad-core Mac Pro.
Is this a happening to anyone else? This product is horrific as it relates to system performance! Any suggestions or tips/tricks to improve performance?
Please help! Thinking of going back to Aperture 2.
Jesse

http://discussions.apple.com/thread.jspa?threadID=2334088&tstart=0
It hasn't spent much time off the first page of the forum.
Ian

Similar Messages

  • Is there a documented correlation between high CPU/RAM usage and poor system performance?

    I realize this subject is not black and white and has quite a bit of depth to it as high usage of either the CPU or RAM does not necessarily mean that a computer is running slowly.
    However, is there any documentation, scientific research or academic journal that makes a correlation between poor system performance and the consumption of system resources.
    It goes without saying that if you use all your RAM then there won't be any available for additional programs, but can this be substantiated with metrical data?

    Check this:
    http://superuser.com/questions/78362/what-is-the-relationship-between-cpu-usage-and-ram
    http://www.computermemoryupgrade.net/memory-influence-on-performance.html
    Fouad Roumieh

  • Poor Bluetooth performance with all aluminum Mac Pro

    The all aluminum case for pre-mavericks Mac Pro is the primary reason for poor antenna performance of Bluetooth. Aluminum, being a good conductor, acts as a reflector of EMF forming what is known as a Faraday Cage, essentially trapping emissions within the box. Normally, holes drilled in the case would allow enough EMF to pass through the case but the hole size for transmission is directly proportional to the lowest frequency that will pass through easily. An example is the typical microwave oven where the window is actually a conducting sheet with small enough hole such that higher freq light waves pass easily through the sheet but lower frequency microwaves do not. Perhaps if the drive bay covers were made of plastic, transmission of the Bluetooth and wifi would be sufficient. One might carefully nibble a slot or two in the side door but this would surely invalidate any warranty and care would have to be taken not to get aluminum particles inside the computer. This would probably nullify any FCC approval of the machine due to clocking noise interference with other devices. The best approach would probably be a tuned waveguide that passes frequencies only around 2.4 GHz ~ 5 GHz through the case (very similar to the way tuned ports on audio speakers pass a band of frequencies needed to extend bass response). I'm sure Apple will have corrected this design flaw in the new Mac Pro introduced this year. If you have lots of time on your hands you can get a college level text on electromagnetics (Maxwell's Equations, etc.) and derive all the details but with a bit of experimenting and reading about tin can antenna mods to wireless routers you should be able to improve Bluetooth performance significantly.

    Thanks for the suggestion.  I will have to move my wireless home base station.  It is on the same desk as my mini so much less than 5 feet away. 

  • Poor system performance - Macbook Pro

    Hi Folks,
    I got my 15 inch macbook pro on Thanksgiving 2011. the configuration is as follows:
    Processor  2.2 GHz Intel Core i7
    Memory  4 GB 1333 MHz DDR3
    Graphics  Intel HD Graphics 3000 384 MB
    Software  OS X 10.8.2 (12C60)
    I usually dont shut down my laptop every night and put it on sleep mode (Its only when I update a OSX feature I restart the mac)
    lately, over the past few months I have observed - when I open my lid and login, it takes several minutes to open a browser window! sometimes as long as 6-7 minutes. the rainbow cursor is visible for too long duration!
    I felt it might be because of various applications I use. However, there is around 300-400 Mb free memory (I use a app to know this) when I login and I roughly have around 229GB free space.
    can you please share tips and tricks on:
    1. improving system performance
    2. resolving above issue
    Thanks,
    KK
    P.S: I dont use Photoshop!

    Hi etresoft,
    thanks for the reply.
    please find below the details of the program:
    Hardware Information:
        MacBook Pro - model: MacBookPro8,2
        1 2.2 GHz Intel Core i7 CPU: 4 cores
        4 GB RAM
    Startup Items:
        ProTec6b - Path: /Library/StartupItems/ProTec6b
    System Software:
        OS X 10.8.2 (12C60) - Uptime: 0 days 11:14
    Disk Information:
        TOSHIBA MK5065GSXF disk0 : (500.11 GB)
            disk0s1 (disk0s1) <not mounted>: 209.7 MB
            Macintosh HD (disk0s2) /: 499.25 GB (228.78 GB free)
            Recovery HD (disk0s3) <not mounted>: 650 MB
        HL-DT-ST DVDRW  GS31N 
    USB Information:
        Apple Inc. BRCM2070 Hub
            Apple Inc. Bluetooth USB Host Controller
        Apple Inc. Apple Internal Keyboard / Trackpad
        Apple Inc. FaceTime HD Camera (Built-in)
        TigerJet Network, Inc. USB Internet Phone by TigerJet 18.6 MB
        Apple Computer, Inc. IR Receiver
    FireWire Information:
    Kernel Extensions:
    Problem System Launch Daemons:
               [failed]    com.apple.xprotectupdater.plist
    Problem System Launch Agents:
               [failed]    com.apple.afpstat.plist
    Launch Daemons:
               [loaded]    com.adobe.fpsaud.plist
               [loaded]    com.google.keystone.daemon.plist
               [loaded]    com.microsoft.office.licensing.helper.plist
               [loaded]    Nalpeirond6b.plist
    Launch Agents:
               [loaded]    com.google.keystone.agent.plist
               [loaded]    com.sony.PMBPortable.AutoRun.plist
    User Launch Agents:
               [loaded]    com.adobe.ARM.202f4087f2bbde52e3ac2df389f53a4f123223c9cc56a8fd83a6f7ae.plist
               [loaded]    com.divx.agent.postinstall.plist
               [loaded]    com.facebook.videochat.kunalkulkarni.plist
               [loaded]    com.microsoft.LaunchAgent.SyncServicesAgent.plist
    User Login Items:
        None
    3rd Party Preference Panes:
        DivX
        Flash Player
        Flip4Mac WMV
    Internet Plug-ins:
        AdobePDFViewer.plugin
        AdobePDFViewerNPAPI.plugin
        AmazonMP3DownloaderPlugin1017277.plugin
        DivXBrowserPlugin.plugin
        Flash Player.plugin
        FlashPlayer-10.6.plugin
        Flip4Mac WMV Plugin.plugin
        googletalkbrowserplugin.plugin
        JavaAppletPlugin.plugin
        npgtpo3dautoplugin.plugin
        OVSHelper.plugin
        QuickTime Plugin.plugin
        SharePointBrowserPlugin.plugin
        Silverlight.plugin
    User Internet Plug-ins:
        Google Earth Web Plug-in.plugin
    Bad Fonts:
        None
    Top Processes:
        9.0   %    mj_dev
        4.8   %    GMATPrep
        4.0   %    coreaudiod
        3.0   %    mds
        1.5   %    WindowServer
        1.2   %    EtreCheck
        0.9   %    iTunes
        0.7   %    magicJack
        0.4   %    ocspd
        0.3   %    fontd
    I am really fed up of the Macbook due to significant delay in running programs
    any type of help is appreciated.
    thanks,
    KK

  • Poor System performance after EHP4 upgrade

    Hello Experts,
    We have just finished our Upgrade to EHP4 for ECC6 system. After the upgrade we are noticing awfully slow system response time.
    My SGEN is currently executing and it's showing another 45 hours before it is finished.  Are there specific post Upgrade activities that I am missing? Once I try to perform some action it takes ages to compile the program. I undesratand that since SGEN is not run yet so it will need some time to compile and generate load for the application but still the response is takinng agaes before I see the actual Application/Program active in GUI.
    Please suggest what I can do to boost up my system performance.
    Thanks,
    M

    Hi Sunny,
    Another Update
    I looked at SAP Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel
    Following is the recommnedation:
    Implement the SAP profile parameters as follows:
    em/initial_size_MB 1024 up to 1TB (note 835474)
    em/blocksize_KB 2048, 4096 or 8192 (note 835474)
    ztta/roll_first 1
    ztta/roll_area 6500000
    The deafult value of the following parameters is 2000000000 (2GB).
    They can be changed depending on the HW (RAM) and the configured
    SWAP Space:
    ztta/roll_extension 2000000000 (2GB)
    abap/heap_area_dia 2000000000 (2GB)
    abap/heap_area_nondia 2000000000 (2GB)
    abap/heap_area_total 2000000000 (2GB)
    But same SAP Note refers for windows:
    For Windows 64Bit recommendations see note 88416:
    As per this note recommendations are as follows:
    Standard values for zero administration memory management
    [HS] = size of the physical main memory
    [PM] = value of the profile parameter PHYS_MEMSIZE (standard value=[HS])
    [BE] = maximum possible number of users (calculated from [PM])
    Profile parameter
    Standard 32-bit
    Standard 64-bit
    Unit
    em/initial_size_MB
        [PM]
        [PM]
    Mbyte
    ---    em/max_size_MB
    ---    20000
    ---   100000
    Mbyte
    em/address_space_MB
        512
       4096
    Mbyte
      ztta/roll_first
        1
        1
    Byte
    ---    ztta/roll_area
    ---  2000000
    ---  3000000
    Byte
    ztta/roll_extension
    2000000000
    2000000000
    Byte
    abap/heap_area_dia
    2000000000
    2000000000
    Byte
    abap/heap_area_nondia
    2000000000
    0
    Byte
    abap/heap_area_total
    2000000000
    [PM]*1048576
    Byte
    -    rdisp/ROLL_MAXFS
    [BE] * 100
    [BE] * 100
    8KB Block
    ---    rdisp/ROLL_SHM
    [BE] * 100
    [BE] * 100
    8KB Block
    ---    rdisp/PG_MAXFS
    ---    32768
    ---                          32768
    8KB Block
        rdisp/PG_SHM
    [BE] * 50
    BE] * 50
    8KB Block
    PLease note that ours is a 64Bit kernel for WIndows 2003
    x86_64
    So is it ok to change the value of abap/heap_area_nondia  ?
    Thanks,
    M

  • Very poor network performance with a G4

    I have a white & grey G4 (1.25GHz and 256MB) running OS X 10.4.5. It's exhibiting very poor network performance, e.g. it will not FTP files over a LAN at more than about 40KB/second.
    Other nodes on the same switch perform fine, as do other ports on the switch. The machine is set to autodetect for speed & duplex, so my question is -- how do I debug this? I've tried swapping network cables already...
    Thanks!
    Chris

    This came down to an incompatibility between the G4 and the Cisco. When the switch is set to force 100Mbit but negotiate duplex, the G4 doesn't like it. Going back to auto speed & duplex fixed the problem...

  • Poor performance with aperture 3.1.1 on macbookpro

    Installed aperture 3.1.1 and imported my old iphoto library with approximately 12k images.
    I have already disabled faces but still have serious performance issues with: a) opening aperture, b) browsing the library, c) clicking an image in the library or importing an image. Program is not workable basically.
    Currently running 10.6.5 on a Macbookpro 5,1 with 4gb ram
    Hope someone can help

    How long (days, hours) have you given Aperture to process the import?
    It can take more than a day (depends on many things).
    If you haven't yet let Aperture run unmolested for at least a full night, do so now. Be sure to have your MBP plugged in, on, open, and set to not sleep.
    If you have already let Aperture run for many hours, your next step is to go through the usual trouble-shooting. I'd start with "Rebuild Library". This may take hours or even a full day. It may be simpler to delete your current Library, create a new one, and import your iPhoto photos into it.
    Before that, check "Window→Show Activity". Any processing going on in the background? (Aperture does, IME, continue to process even when nothing shows in its Activity Window.)
    Your hardware is adequate to the task of running Aperture.

  • Unexplainably poor system performance??

    I have been experiencing unusually poor performance from my system in running games and applications. There has been some serious system instability issues, system crashes, spontaneous resettings, and failures to read from my optical drives. I have all the latest drivers installed for everything including bios updates. I have the bios set  to default settings and everything seems to be reporting that it is working correctly. however all my benchmark scores from sandra lite, 3dmark and the usual others are almost half that of almost identical systems. I am not even able to run the nvidia geforce 6800 demos, they load, but either run at 1 fps or show a still image of the demo. In the memory bandwidth benchmark in sandra lite it gives me a note that says my cpu is bandwidth limited, and that i should upgrade to faster memory. Could my problems be a memory issue, or possibly a power supply problem? i have a generic P.O.S. power supply by the way. This is very strange, thanks for the help!
    System Specs:
    MSI neo6 platium p4865 mb
    pentium 4 3.0ghz prescott
    512 mb ddr 333 pc 2700
    geforce 6800 agp 8x 128mb
    bios: default settings no overclocking

    Ok, i have been running spybot and adaware regularly and my system seems to be clean of virus' and spyware. It should be noted that my poor performance does not occur during simple operations such as browsing the internet or using office applications. The strange things start to happen only when the system is utilizing the graphics and memory more stressfully, such as when i run the nvidia demos, or 3dmark, the computer acts as if it is trying to run something that is way too demanding of the hardware when i know it is not. I also have very inconsistent startups, sometimes the computer will hang at the windowsxp startup screen and i'll have to hit the reset buton and then inthe windows startup menu select "last known configuration that worked" to get it to start up after no software modifications. The os is a new install, i have done nothing to windows except update to the latest software and drivers. Do u think formatting and reinstalling will really fix this? Thanks for the replys by the way.
    Update: I just installed a new power supply, Antech Trupower 430 with no difference in performance whatsoever, the cpu does seem to run a little cooler though.

  • Poor restore performance with MaxDB 7.6.04.15 and HP Data Protector 6

    We encounter severe problems with the MaxDB integration in Data Protector 6. While the backup is finished in two hours (LTO4), the restore takes 9-12 hours.
    The source system has the following specs:
    CPU: 4x QuadCore
    RAM: 48 GB
    Cache Size: 25 GB
    db size (allocated): 550 GB
    27x 30 GB raw devices, located in SAN
    SLES 10 SP2
    parallelism (# pipes): 14 (tried 4, 8, 28, 2 tapes...)
    Target system:
    CPU: 2x DualCore
    RAM: 8 GB
    Cache Size: 4 GB
    27x 30 GB raw devices, located in SAN
    SLES 10 SP2
    We checked the performance of file system restores - works fine with good restore times, so we don't think it's a SAN/tape library issue (e. g. switches etc.).
    Some things are quite disturbing:
    x_cons <SID> show sus
    SERVERDB: <SID>
    List of suspend-reasons:
    ========================
    Total Suspends: 428083
    Vsuspend (203) :  426288 (  99.58% ) kb39read_wait
    Vsuspend (204) :    1611 (   0.38% ) kb39write_wait
    JobWait BckRec :       1 (   0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
    No-Work  (255) :     183 (   0.04% ) Task is waiting for work
    x_cons <SID> show tasks|grep BUP
    T71    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T72    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T73    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T74    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T75    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T76    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T77    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T78    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T79    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T80    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T81    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T82    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T83    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T84    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T85    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T86    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T87    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T88    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T89    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    T92    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T109   6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    T111   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T112   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T128   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T129   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T130   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T131   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T132   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T133   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T134   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T135   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T136   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T137   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T138   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T139   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T140   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T141   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T142   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T143   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T144   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    T148   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
    2008-09-16 15:54:01  6300     20235 RTE       ADMIN=1
    2008-09-16 15:54:01  6300     20235 RTE       _AK_DUMP_ALLOWED=YES
    2008-09-16 15:54:01  6300     20235 RTE       ALLOW_MULTIPLE_SERVERTASK_UKTS=YES
    2008-09-16 15:54:01  6300     20235 RTE       AUTHENTICATION_ALLOW=
    2008-09-16 15:54:01  6300     20235 RTE       AUTHENTICATION_DENY=
    2008-09-16 15:54:01  6300     20235 RTE       AUTOSAVE=1
    2008-09-16 15:54:01  6300     20235 RTE       AUTO_RECREATE_BAD_INDEXES=YES
    2008-09-16 15:54:01  6300     20235 RTE       BACKUPRESULT=1
    2008-09-16 15:54:01  6300     20235 RTE       BACKUP_BLOCK_CNT=64
    2008-09-16 15:54:01  6300     20235 RTE       _BACKUP_HISTFILE=dbm.knl
    2008-09-16 15:54:01  6300     20235 RTE       _BACKUP_MED_DEF=dbm.mdf
    2008-09-16 15:54:01  6300     20235 RTE       CACHE_IN_SHARED_MEMORY=NO
    2008-09-16 15:54:01  6300     20235 RTE       CACHE_SIZE=512000
    2008-09-16 15:54:01  6300     20235 RTE       CALLSTACKLEVEL=0
    2008-09-16 15:54:01  6300     20235 RTE       _CAT_CACHE_MINSIZE=262144
    2008-09-16 15:54:01  6300     20235 RTE       CAT_CACHE_SUPPLY=12864
    2008-09-16 15:54:01  6300     20235 RTE       CHECKDATA=1
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_BACKUP=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_COMMON=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_CONVERTER=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_DATACACHE=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_DATAINDEX=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_DATAPAGELOG=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_FBM=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_HASHED_RESULTSET=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_IOMAN=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_KB_REGIONS=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOCK_SUPPLY=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOCK=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOGHISTORY=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOGPAGE=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOGTRANS=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_LOGVOLUME=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_QUERYREWRITE=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_REGIONS=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_SRVTASKS=0
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_TABLE_WIDTH=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_TASK_SPECIFIC_CATALOGCACHE=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_TRANSLIST=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_TREE_LOCKS=NO
    2008-09-16 15:54:01  6300     20235 RTE       CHECK_TREE=NO
    2008-09-16 15:54:01  6300     20235 RTE       CLUSTERED_LOBS=NO
    2008-09-16 15:54:01  6300     20235 RTE       CLUSTER_WRITE_THRESHOLD=80
    2008-09-16 15:54:01  6300     20235 RTE       COLUMNCOMPRESSION=YES
    2008-09-16 15:54:01  6300     20235 RTE       _COMMENT=
    2008-09-16 15:54:01  6300     20235 RTE       CONTROLPASSWORD=***
    2008-09-16 15:54:01  6300     20235 RTE       CONTROLUSERID=CONTROL
    2008-09-16 15:54:01  6300     20235 RTE       CONVERTER_REGIONS=64
    2008-09-16 15:54:01  6300     20235 RTE       DATABASEFULL=1
    2008-09-16 15:54:01  6300     20235 RTE       _DATA_CACHE_RGNS=64
    2008-09-16 15:54:01  6300     20235 RTE       DATA_IO_BLOCK_COUNT=64
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_GROUPS=1
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0001=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0002=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0003=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0004=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0005=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0006=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0007=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0008=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0009=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0010=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0011=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0012=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0013=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0014=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0015=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0016=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0017=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0018=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0019=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0020=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0021=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0022=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0023=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0024=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0025=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0026=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_MODE_0027=NORMAL
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0001=/dev/raw/raw1
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0002=/dev/raw/raw2
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0003=/dev/raw/raw3
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0004=/dev/raw/raw4
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0005=/dev/raw/raw5
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0006=/dev/raw/raw6
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0007=/dev/raw/raw7
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0008=/dev/raw/raw8
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0009=/dev/raw/raw9
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0010=/dev/raw/raw10
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0011=/dev/raw/raw11
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0012=/dev/raw/raw12
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0013=/dev/raw/raw13
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0014=/dev/raw/raw14
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0015=/dev/raw/raw15
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0016=/dev/raw/raw16
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0017=/dev/raw/raw17
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0018=/dev/raw/raw18
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0019=/dev/raw/raw19
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0020=/dev/raw/raw20
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0021=/dev/raw/raw21
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0022=/dev/raw/raw22
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0023=/dev/raw/raw23
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0024=/dev/raw/raw24
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0025=/dev/raw/raw25
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0026=/dev/raw/raw26
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_NAME_0027=/dev/raw/raw27
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0001=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0002=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0003=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0004=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0005=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0006=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0007=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0008=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0009=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0010=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0011=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0012=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0013=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0014=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0015=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0016=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0017=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0018=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0019=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0020=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0021=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0022=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0023=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0024=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0025=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0026=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_SIZE_0027=3932160
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0001=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0002=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0003=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0004=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0005=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0006=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0007=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0008=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0009=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0010=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0011=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0012=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0013=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0014=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0015=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0016=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0017=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0018=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0019=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0020=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0021=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0022=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0023=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0024=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0025=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0026=R
    2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0027=R
    2008-09-16 15:54:01  6300     20235 RTE       DATE_TIME_FORMAT=INTERNAL
    2008-09-16 15:54:01  6300     20235 RTE       DBFILLINGABOVELIMIT=70L80M85M90H95H96H97H98H99H
    2008-09-16 15:54:01  6300     20235 RTE       DBFILLINGBELOWLIMIT=70L80L85L90L95L
    2008-09-16 15:54:01  6300     20235 RTE       DDLTRIGGER=YES
    2008-09-16 15:54:01  6300     20235 RTE       DEADLOCK_DETECTION=4
    2008-09-16 15:54:01  6300     20235 RTE       DEFAULT_CODE=ASCII
    2008-09-16 15:54:01  6300     20235 RTE       _DELAY_COMMIT=NO
    2008-09-16 15:54:01  6300     20235 RTE       _DELAY_LOGWRITER=0
    2008-09-16 15:54:01  6300     20235 RTE       DIAG_HISTORY_NUM=2
    2008-09-16 15:54:01  6300     20235 RTE       DIAG_HISTORY_PATH=/sapdb/data/wrk/PSR/DIAGHISTORY
    2008-09-16 15:54:01  6300     20235 RTE       _DIAG_SEM=0
    2008-09-16 15:54:01  6300     20235 RTE       _DW_IO_AREA_FLUSH=50
    2008-09-16 15:54:01  6300     20235 RTE       _DW_IO_AREA_SIZE=50
    2008-09-16 15:54:01  6300     20235 RTE       _DW_LRU_TAIL_FLUSH=25
    2008-09-16 15:54:01  6300     20235 RTE       _DYN_TASK_STACK=NO
    2008-09-16 15:54:01  6300     20235 RTE       ENABLE_CHECK_INSTANCE=YES
    2008-09-16 15:54:01  6300     20235 RTE       ENABLE_SYSTEM_TRIGGERS=YES
    2008-09-16 15:54:01  6300     20235 RTE       ERROR=3
    2008-09-16 15:54:01  6300     20235 RTE       _EVENTFILE=knldiag.evt
    2008-09-16 15:54:01  6300     20235 RTE       _EVENTSIZE=0
    2008-09-16 15:54:01  6300     20235 RTE       EVENT=1
    2008-09-16 15:54:01  6300     20235 RTE       EXPAND_COM_TRACE=NO
    2008-09-16 15:54:01  6300     20235 RTE       EXTERNAL_DUMP_REQUEST=NO
    2008-09-16 15:54:01  6300     20235 RTE       FBM_CLUSTER_MODE=MIXED
    2008-09-16 15:54:01  6300     20235 RTE       _FBM_LOW_IO_RATE=10
    2008-09-16 15:54:01  6300     20235 RTE       FBM_VOLUME_BALANCE=10
    2008-09-16 15:54:01  6300     20235 RTE       FBM_VOLUME_COMPRESSION=50
    2008-09-16 15:54:01  6300     20235 RTE       FILEDIR_SPINLOCKPOOL_SIZE=10
    2008-09-16 15:54:01  6300     20235 RTE       FORBID_LOAD_BALANCING=YES
    2008-09-16 15:54:01  6300     20235 RTE       FORMATTING_MODE=PARALLEL
    2008-09-16 15:54:01  6300     20235 RTE       FORMAT_DATAVOLUME=YES
    2008-09-16 15:54:01  6300     20235 RTE       HASHED_RESULTSET_CACHESIZE=262144
    2008-09-16 15:54:01  6300     20235 RTE       HASHED_RESULTSET=YES
    2008-09-16 15:54:01  6300     20235 RTE       HEAP_CHECK_LEVEL=0
    2008-09-16 15:54:01  6300     20235 RTE       HIRES_TIMER_TYPE=CPU
    2008-09-16 15:54:01  6300     20235 RTE       HS_STORAGE_DLL=libhsscopy
    2008-09-16 15:54:01  6300     20235 RTE       HS_SYNC_INTERVAL=50
    2008-09-16 15:54:01  6300     20235 RTE       _IDXFILE_LIST_SIZE=2048
    2008-09-16 15:54:01  6300     20235 RTE       INDEX_LEAF_CACHING=2
    2008-09-16 15:54:01  6300     20235 RTE       INIT_ALLOCATORSIZE=262144
    2008-09-16 15:54:01  6300     20235 RTE       INSTANCE_TYPE=OLTP
    2008-09-16 15:54:01  6300     20235 RTE       _IOPROCS_FOR_PRIO=0
    2008-09-16 15:54:01  6300     20235 RTE       _IOPROCS_FOR_READER=1
    2008-09-16 15:54:01  6300     20235 RTE       _IOPROCS_PER_DEV=2
    2008-09-16 15:54:01  6300     20235 RTE       _IOPROCS_SWITCH=2
    2008-09-16 15:54:01  6300     20235 RTE       JOIN_MAXTAB_LEVEL4=64
    2008-09-16 15:54:01  6300     20235 RTE       JOIN_MAXTAB_LEVEL9=5
    2008-09-16 15:54:01  6300     20235 RTE       JOIN_SEARCH_LEVEL=0
    2008-09-16 15:54:01  6300     20235 RTE       JOIN_TABLEBUFFER=128
    2008-09-16 15:54:01  6300     20235 RTE       _KERNELDIAGFILE=knldiag
    2008-09-16 15:54:01  6300     20235 RTE       KERNELDIAGSIZE=800
    2008-09-16 15:54:01  6300     20235 RTE       _KERNELDUMPFILE=knldump
    2008-09-16 15:54:01  6300     20235 RTE       _KERNELTRACEFILE=knltrace
    2008-09-16 15:54:01  6300     20235 RTE       KERNELTRACESIZE=2809
    2008-09-16 15:54:01  6300     20235 RTE       KERNELVERSION=KERNEL    7.6.04   BUILD 015-123-189-221
    2008-09-16 15:54:01  6300     20235 RTE       _LM_LOCK_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       _LM_REQUEST_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       _LM_TRANS_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       LOAD_BALANCING_CHK=0
    2008-09-16 15:54:01  6300     20235 RTE       LOAD_BALANCING_DIF=10
    2008-09-16 15:54:01  6300     20235 RTE       LOAD_BALANCING_EQ=5
    2008-09-16 15:54:01  6300     20235 RTE       LOCAL_REDO_LOG_BUFFER_SIZE=0
    2008-09-16 15:54:01  6300     20235 RTE       _LOCKMANAGER_ENABLED=NO
    2008-09-16 15:54:01  6300     20235 RTE       _LOCK_SUPPLY_BLOCK=100
    2008-09-16 15:54:01  6300     20235 RTE       LOGABOVELIMIT=50L75L90M95M96H97H98H99H
    2008-09-16 15:54:01  6300     20235 RTE       LOGFULL=1
    2008-09-16 15:54:01  6300     20235 RTE       LOGSEGMENTFULL=1
    2008-09-16 15:54:01  6300     20235 RTE       LOG_BACKUP_TO_PIPE=NO
    2008-09-16 15:54:01  6300     20235 RTE       LOG_IO_BLOCK_COUNT=8
    2008-09-16 15:54:01  6300     20235 RTE       LOG_IO_QUEUE=200
    2008-09-16 15:54:01  6300     20235 RTE       LOG_MIRRORED=NO
    2008-09-16 15:54:01  6300     20235 RTE       LOG_QUEUE_COUNT=1
    2008-09-16 15:54:01  6300     20235 RTE       LOG_SEGMENT_SIZE=129024
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_NAME_001=/dev/raw/raw28
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_NAME_002=/dev/raw/raw29
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_SIZE_001=524288
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_SIZE_002=524288
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_TYPE_001=R
    2008-09-16 15:54:01  6300     20235 RTE       LOG_VOLUME_TYPE_002=R
    2008-09-16 15:54:01  6300     20235 RTE       LRU_FOR_SCAN=NO
    2008-09-16 15:54:01  6300     20235 RTE       MAXBACKUPDEVS=32
    2008-09-16 15:54:01  6300     20235 RTE       MAXCPU=3
    2008-09-16 15:54:01  6300     20235 RTE       MAXDATAVOLUMES=40
    2008-09-16 15:54:01  6300     20235 RTE       _MAXEVENTS=100
    2008-09-16 15:54:01  6300     20235 RTE       _MAXEVENTTASKS=2
    2008-09-16 15:54:01  6300     20235 RTE       _MAXGARBAGE_COLL=1
    2008-09-16 15:54:01  6300     20235 RTE       MAXLOCKS=1000000
    2008-09-16 15:54:01  6300     20235 RTE       MAXLOGVOLUMES=4
    2008-09-16 15:54:01  6300     20235 RTE       MAXPAGER=64
    2008-09-16 15:54:01  6300     20235 RTE       MAXRGN_REQUEST=-1
    2008-09-16 15:54:01  6300     20235 RTE       MAXSERVERTASKS=116
    2008-09-16 15:54:01  6300     20235 RTE       _MAXTASK_STACK=512
    2008-09-16 15:54:01  6300     20235 RTE       _MAXTRANS=1604
    2008-09-16 15:54:01  6300     20235 RTE       MAXUSERTASKS=200
    2008-09-16 15:54:01  6300     20235 RTE       MAXVOLUMES=45
    2008-09-16 15:54:01  6300     20235 RTE       MAX_HASHTABLE_MEMORY=5120
    2008-09-16 15:54:01  6300     20235 RTE       MAX_LOG_QUEUE_COUNT=0
    2008-09-16 15:54:01  6300     20235 RTE       _MAX_MESSAGE_FILES=0
    2008-09-16 15:54:01  6300     20235 RTE       MAX_MESSAGE_LIST_LENGTH=100
    2008-09-16 15:54:01  6300     20235 RTE       MAX_RETENTION_TIME=480
    2008-09-16 15:54:01  6300     20235 RTE       MAX_SERVERTASK_STACK=500
    2008-09-16 15:54:01  6300     20235 RTE       MAX_SINGLE_HASHTABLE_SIZE=512
    2008-09-16 15:54:01  6300     20235 RTE       MAX_SPECIALTASK_STACK=500
    2008-09-16 15:54:01  6300     20235 RTE       _MBLOCK_DATA_SIZE=32768
    2008-09-16 15:54:01  6300     20235 RTE       _MBLOCK_QUAL_SIZE=32768
    2008-09-16 15:54:01  6300     20235 RTE       _MBLOCK_STACK_SIZE=32768
    2008-09-16 15:54:01  6300     20235 RTE       _MBLOCK_STRAT_SIZE=16384
    2008-09-16 15:54:01  6300     20235 RTE       MCOD=NO
    2008-09-16 15:54:01  6300     20235 RTE       MEMORY_ALLOCATION_LIMIT=0
    2008-09-16 15:54:01  6300     20235 RTE       _MINREPLY_SIZE=4096
    2008-09-16 15:54:01  6300     20235 RTE       MINSERVERTASKS=116
    2008-09-16 15:54:01  6300     20235 RTE       MIN_RETENTION_TIME=60
    2008-09-16 15:54:01  6300     20235 RTE       MONITOR_READ=2147483647
    2008-09-16 15:54:01  6300     20235 RTE       MONITOR_ROWNO=0
    2008-09-16 15:54:01  6300     20235 RTE       MONITOR_SELECTIVITY=0
    2008-09-16 15:54:01  6300     20235 RTE       MONITOR_TIME=2147483647
    2008-09-16 15:54:01  6300     20235 RTE       _MP_DISP_LOOPS=2
    2008-09-16 15:54:01  6300     20235 RTE       _MP_DISP_PRIO=DEFAULT
    2008-09-16 15:54:01  6300     20235 RTE       _MP_RGN_BUSY_WAIT=DEFAULT
    2008-09-16 15:54:01  6300     20235 RTE       _MP_RGN_DIRTY_READ=DEFAULT
    2008-09-16 15:54:01  6300     20235 RTE       MP_RGN_LOOP=-1
    2008-09-16 15:54:01  6300     20235 RTE       _MP_RGN_PRIO=DEFAULT
    2008-09-16 15:54:01  6300     20235 RTE       _MP_RGN_QUEUE=YES
    2008-09-16 15:54:01  6300     20235 RTE       NO_SYNC_TO_DISK_WANTED=NO
    2008-09-16 15:54:01  6300     20235 RTE       OFFICIAL_NODE=
    2008-09-16 15:54:01  6300     20235 RTE       OMS_HEAP_BLOCKSIZE=10000
    2008-09-16 15:54:01  6300     20235 RTE       OMS_HEAP_COUNT=8
    2008-09-16 15:54:01  6300     20235 RTE       OMS_HEAP_LIMIT=0
    2008-09-16 15:54:01  6300     20235 RTE       OMS_HEAP_THRESHOLD=100
    2008-09-16 15:54:01  6300     20235 RTE       _OMS_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       _OMS_RGNS=7
    2008-09-16 15:54:01  6300     20235 RTE       OMS_RUN_IN_UDE_SERVER=NO
    2008-09-16 15:54:01  6300     20235 RTE       OMS_STREAM_TIMEOUT=30
    2008-09-16 15:54:01  6300     20235 RTE       OMS_VERS_THRESHOLD=2097152
    2008-09-16 15:54:01  6300     20235 RTE       ONLINE=1
    2008-09-16 15:54:01  6300     20235 RTE       OPMSG1=/dev/console
    2008-09-16 15:54:01  6300     20235 RTE       OPMSG2=/dev/null
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_AGGREGATION=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_FETCH_REVERSE=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_FIRST_ROWS=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_HASHTABLE=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_HASH_MINIMAL_RATIO=1
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_ONEPHASE=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_OPERATOR_SORT=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_OUTER=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_PARALLEL_MINSIZE=1000000
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_JOIN_PARALLEL_SERVERS=0
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_MIN_MAX=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_OPERATOR_JOIN_COSTFUNC=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_OPERATOR_JOIN=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_QUAL_ON_INDEX=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_QUERYREWRITE=OPERATOR
    2008-09-16 15:54:01  6300     20235 RTE       OPTIMIZE_STAR_JOIN=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIM_CACHE=NO
    2008-09-16 15:54:01  6300     20235 RTE       OPTIM_INV_ONLY=YES
    2008-09-16 15:54:01  6300     20235 RTE       OPTIM_JOIN_FETCH=0
    2008-09-16 15:54:01  6300     20235 RTE       OPTIM_MAX_MERGE=500
    2008-09-16 15:54:01  6300     20235 RTE       OUTOFSESSIONS=3
    2008-09-16 15:54:01  6300     20235 RTE       _PACKET_SIZE=131072
    2008-09-16 15:54:01  6300     20235 RTE       _PAGE_SIZE=8192
    2008-09-16 15:54:01  6300     20235 RTE       PREALLOCATE_IOWORKER=NO
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_BASE_COM=10
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_BASE_IOC=80
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_BASE_RAV=80
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_BASE_REX=40
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_BASE_U2U=100
    2008-09-16 15:54:01  6300     20235 RTE       _PRIO_FACTOR=80
    2008-09-16 15:54:01  6300     20235 RTE       PROTECT_DATACACHE_MEMORY=NO
    2008-09-16 15:54:01  6300     20235 RTE       _READAHEAD_BLOBS=32
    2008-09-16 15:54:01  6300     20235 RTE       REQUEST_TIMEOUT=5000
    2008-09-16 15:54:01  6300     20235 RTE       RESERVEDSERVERTASKS=75
    2008-09-16 15:54:01  6300     20235 RTE       _RESTART_TIME=600
    2008-09-16 15:54:01  6300     20235 RTE       ROW_LOCKS_PER_TRANSACTION=50
    2008-09-16 15:54:01  6300     20235 RTE       _ROW_RGNS=8
    2008-09-16 15:54:01  6300     20235 RTE       _RTEDUMPFILE=rtedump
    2008-09-16 15:54:01  6300     20235 RTE       RTE_TEST_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       RUNDIRECTORY=/sapdb/data/wrk/PSR
    2008-09-16 15:54:01  6300     20235 RTE       SEQUENCE_CACHE=1
    2008-09-16 15:54:01  6300     20235 RTE       _SERVERDB_FOR_SAP=YES
    2008-09-16 15:54:01  6300     20235 RTE       SESSION_TIMEOUT=900
    2008-09-16 15:54:01  6300     20235 RTE       SET_VOLUME_LOCK=YES
    2008-09-16 15:54:01  6300     20235 RTE       SHAREDSQL_CLEANUPTHRESHOLD=25
    2008-09-16 15:54:01  6300     20235 RTE       SHAREDSQL_COMMANDCACHESIZE=262144
    2008-09-16 15:54:01  6300     20235 RTE       SHAREDSQL=YES
    2008-09-16 15:54:01  6300     20235 RTE       _SHMKERNEL=24377
    2008-09-16 15:54:01  6300     20235 RTE       SHOW_MAX_KB_STACK_USE=NO
    2008-09-16 15:54:01  6300     20235 RTE       SHOW_MAX_STACK_USE=NO
    2008-09-16 15:54:01  6300     20235 RTE       SIMULATE_VECTORIO=NEVER
    2008-09-16 15:54:01  6300     20235 RTE       SPINLOCK_BACKOFF_BASE=1
    2008-09-16 15:54:01  6300     20235 RTE       SPINLOCK_BACKOFF_FACTOR=2
    2008-09-16 15:54:01  6300     20235 RTE       SPINLOCK_BACKOFF_MAXIMUM=64
    2008-09-16 15:54:01  6300     20235 RTE       SPINLOCK_LOOP_COUNT=30000
    2008-09-16 15:54:01  6300     20235 RTE       STANDBY=1
    2008-09-16 15:54:01  6300     20235 RTE       SUBTREE_LOCKS=NO
    2008-09-16 15:54:01  6300     20235 RTE       SUPPRESS_CORE=YES
    2008-09-16 15:54:01  6300     20235 RTE       SYMBOL_DEMANGLING=NO
    2008-09-16 15:54:01  6300     20235 RTE       SYMBOL_RESOLUTION=YES
    2008-09-16 15:54:01  6300     20235 RTE       SYSTEMERROR=3
    2008-09-16 15:54:01  6300     20235 RTE       _TAB_RGNS=8
    2008-09-16 15:54:01  6300     20235 RTE       _TASKCLUSTER_01=tw;al;ut;100*bup;10*ev,10*gc;
    2008-09-16 15:54:01  6300     20235 RTE       _TASKCLUSTER_02=ti,100*dw;67*us,39*sv;
    2008-09-16 15:54:01  6300     20235 RTE       _TASKCLUSTER_03=equalize
    2008-09-16 15:54:01  6300     20235 RTE       TIME_MEASUREMENT=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_AK=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_ALLOCATOR=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_CATALOG=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_CLIENTKERNELCOM=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_COMMON=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_COMMUNICATION=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_CONVERTER=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DATACACHE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DATACHAIN=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DATAINDEX=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DATAPAM=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DATATREE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DBPROC=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DEFAULT=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_DELETE=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_FBM=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_FILEDIR=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_FRAMECTRL=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_INDEX=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_INSERT=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_IOMAN=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_IPC=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_JOIN=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_KSQL=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOCKMANAGER=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOCK=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOGACTION=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOGHISTORY=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOGPAGE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOGTRANS=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LOGVOLUME=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_LONG=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_MEMORY=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_MESSAGES=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECTCONTAINER=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECT_ADD=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECT_ALTER=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECT_FREE=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECT_GET=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OBJECT=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_CONTAINERDIR=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_CONTEXT=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_ERROR=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_FLUSHCACHE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_INTERFACE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_KEYRANGE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_KEY=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_LOCK=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_MEMORY=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_NEWOBJ=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_SESSION=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_STREAM=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_VAROBJECT=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OMS_VERSION=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_OPTIMIZE=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_ORDER_STANDARD=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_ORDER=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGER=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_BUP=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_EV=2
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_GC=20
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_LW=5
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_PG=3
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_SV=5
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_TI=2
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_US=10
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES_UT=5
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PAGES=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_PRIMARY_TREE=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_QUERYREWRITE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_RUNTIME=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SELECT=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SHAREDSQL=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SQLMANAGER=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SRVTASKS=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_STOP_ERRORCODE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SYNCHRONISATION=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_SYSVIEW=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_TABLE=0
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_TIME=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_UPDATE=NO
    2008-09-16 15:54:01  6300     20235 RTE       TRACE_VOLUME=0
    2008-09-16 15:54:01  6300     20235 RTE       TRANS_HISTORY_SIZE=0
    2008-09-16 15:54:01  6300     20235 RTE       _TRANS_RGNS=8
    2008-09-16 15:54:01  6300     20235 RTE       TRANS_THRESHOLD_VALUE=60
    2008-09-16 15:54:01  6300     20235 RTE       UKT_CPU_RELATIONSHIP=NONE
    2008-09-16 15:54:01  6300     20235 RTE       _UNICODE=YES
    2008-09-16 15:54:01  6300     20235 RTE       UPDATESTAT_PARALLEL_SERVERS=0
    2008-09-16 15:54:01  6300     20235 RTE       UPDATESTAT_SAMPLE_ALGO=1
    2008-09-16 15:54:01  6300     20235 RTE       UPDSTATWANTED=1
    2008-09-16 15:54:01  6300     20235 RTE       USED_MAX_LOG_QUEUE_COUNT=3
    2008-09-16 15:54:01  6300     20235 RTE       USESELECTFETCH=YES
    2008-09-16 15:54:01  6300     20235 RTE       USEUNICODECOLUMNCOMPRESSION=NO
    2008-09-16 15:54:01  6300     20235 RTE       USEVARIABLEINPUT=NO
    2008-09-16 15:54:01  6300     20235 RTE       USE_COROUTINES=YES
    2008-09-16 15:54:01  6300     20235 RTE       _USE_IOPROCS_ONLY=NO
    2008-09-16 15:54:01  6300     20235 RTE       USE_OPEN_DIRECT_FOR_BACKUP=YES
    2008-09-16 15:54:01  6300     20235 RTE       USE_OPEN_DIRECT=YES
    2008-09-16 15:54:01  6300     20235 RTE       USE_SYSTEM_PAGE_CACHE=YES
    2008-09-16 15:54:01  6300     20235 RTE       _UTILITY_PROTFILE=dbm.utl
    2008-09-16 15:54:01  6300     20235 RTE       UTILITY_PROTSIZE=100
    2008-09-16 15:54:01  6300     20235 RTE       VOLUMENO_BIT_COUNT=8
    2008-09-16 15:54:01  6300     20235 RTE       _WORKDATA_SIZE=8192
    2008-09-16 15:54:01  6300     20235 RTE       _WORKSTACK_SIZE=8192
    2008-09-16 15:54:01  6300     20235 RTE       XP_CONVERTER_REGIONS=0
    2008-09-16 15:54:01  6300     20235 RTE       XP_DATA_CACHE_RGNS=0
    2008-09-16 15:54:01  6300     20235 RTE       XP_MAXPAGER=0

    > Some things are quite disturbing:
    >
    >
    x_cons <SID> show sus
    >
    > SERVERDB: <SID>
    >
    > List of suspend-reasons:
    > ========================
    >
    > Total Suspends: 428083
    >
    > Vsuspend (203) :  426288 (  99.58% ) kb39read_wait
    > Vsuspend (204) :    1611 (   0.38% ) kb39write_wait
    > JobWait BckRec :       1 (   0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
    > No-Work  (255) :     183 (   0.04% ) Task is waiting for work
    What exactly do you find disturbing with that information?
    All we see here is how often a specific suspend had been triggered since the database was started. We don't see how long these suspends took and neither do we know what the suspend reason is, that would be important for your current issue.
    >
    x_cons <SID> show tasks|grep BUP
    > T71    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T72    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T73    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T74    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T75    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T76    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T77    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T78    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T79    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T80    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T81    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T82    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T83    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T84    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T85    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T86    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T87    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T88    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T89    6     -1 BUPmed       -1 Vsuspend (203)        0 0               1027577(s)
    > T92    6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T109   6     -1 BUPvol       -1 AsynWaitWrite         0 0               1027577(s)
    > T111   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T112   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T128   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T129   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T130   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T131   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T132   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T133   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T134   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T135   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T136   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T137   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T138   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T139   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T140   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T141   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T142   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T143   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T144   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    > T148   7     -1 BUPvol       -1 AsynWaitWrite         0 0               345248(s)
    Ok, here we see that the MaxDB kernel is waiting for writes to the datavolumes to get finished. As we've only one snapshot here, we cannot tell anything more from it. You either should perform several snapshots in a row, or (better!) use the DBAnalyzer with a short sample interval, say 60 seconds.
    Also you should enable the time measurement, so that we can have some I/O related timing information.
    > I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
    What parameters did you change? Why? And to what values did you set them?
    >
    > 2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0001=R
    > 2008-09-16 15:54:01  6300     20235 RTE       DATA_VOLUME_TYPE_0002=R
    Ok, since you use RAW devices (good choice!) there shouldn't be any issues with the I/O on the OS level.
    What's left is: how are the RAW devices physically stored?
    Could it be that writing to your RAW devices is pretty expensive?
    Ah - before I forget: if you're a SAP customer this should be investigated in a support message!
    Best regards,
    Lars

  • Does anyone else get poor Virtualbox performance with Kernel26-ck?

    I don't know if it's BFS itself or one of my customized options specifically, but if I try to play Netflix inside my Windows XP virtual machine it is terrible and my CPU load is quite high.
    If I boot into the stock Arch kernel I do not have this problem. Anyone else experience this?

    So it seems like it's just me and my config.
    uname -r is different, and I have compiled the kernel modules for it.
    It is only in the last few weeks/month that the performance issue is there.
    Sometimes, when I run the VM, it'll drop me to TTY1 which a bunch of magic output, but it's not a kernel panic. I can switch back to my graphical TTY and everything is fine except the VM is just a black window and has to be forced to close via my WM.
    I'm not sure what kernel config options would do something like this. I have my timer frequency at 1000Hz, which is the main thing I've seen on the Google that can cause problems.
    I am on a Core i3 processor with intel graphics.
    If I post my kernel config, do you think you'd be able to spot anything that would mess up Virtualbox in this subtle way?
    Any ideas? I'm guessing I'm probably on my own.

  • Probable reasons for poor youtube performance with Chrome browser

    Using my new Lenovo Yoga 3 11 inch I have been experiencing horrendeously choppy youtube performance using the chrome browser, which was generating lots of heat due to the demands that chrome was asking of the CPU. The same youtube video plays perfectly smooth using Internet Explorer, and the laptop remains cool thanks to the much lower CPU load. So I was wondering why this was so. I wasted a lot of time following the stock answers of the internet - disabling plugins, 32 bit vs 64 bit chrome, updating drivers, even factory resetting and updating! But after routing through the internet guff, I did find some excellent information that fits my experiences, so I have little reason to doubt that the following statements, extracted from various parts of the internet, are true: Quote: "Google decided that Chrome should always use VP9 codec on PCs – even if there is no hardware acceleration available. This means that Chrome is doing CPU decide and that is pretty demanding in a 3.5w power limit for CPU, GPU, LLC, and FIVR. On IE, YouTube uses H.264/AVC and the hardware codec support kicks in for much more power efficiency." Quote: "When you watch YouTube using Chrome it uses VP8/VP9encoding by default. This type of encoding does not support hardware acceleration (which means it won’t use the on-board GPU – or video chip for you non-techies) so, your CPU has to do all of the work to decode and display the video." I thought people may find this information interesting, expecially if you are using a laptop with a light CPU such as Intel Core M. Chrome is my browser of choice, but this situation has forced me to use Internet Explorer for youtube. 

    I found that Chrome youtube runs much smoother and cooler on my Lenovo Yoga 3 11 inch after installing the h264ify Chrome extension. This allows Chrome to use the h264 codec for youtube instead of the CPU hammering VP9 codec.

  • MacBookPro Performance with Aperture 1.1

    C'mon then, wossit like?!?! If anyone can compare against other machines (PowePC and Intel) then that would be awesome.

    How long (days, hours) have you given Aperture to process the import?
    It can take more than a day (depends on many things).
    If you haven't yet let Aperture run unmolested for at least a full night, do so now. Be sure to have your MBP plugged in, on, open, and set to not sleep.
    If you have already let Aperture run for many hours, your next step is to go through the usual trouble-shooting. I'd start with "Rebuild Library". This may take hours or even a full day. It may be simpler to delete your current Library, create a new one, and import your iPhoto photos into it.
    Before that, check "Window→Show Activity". Any processing going on in the background? (Aperture does, IME, continue to process even when nothing shows in its Activity Window.)
    Your hardware is adequate to the task of running Aperture.

  • Poor OpenGL performance with my laptop

    Hello.
    I have installed Archlinux on my nvidia desktop computer and I can play opengl games smoothly. But the problem is with my laptop. I remember, long time ago , when opengl ran pretty well with linux compared to windows. Since one month ago, I've had windows and Arch on my laptop, when I tried to play Openarena, it ran much better on windows than linux, what has happened to intel driver? Now I only have linux and want to continue playing and it's impossible with that performance.
    I've read many posts and I've failed in my purpose, I'm missing something...
    $ lspci | grep -i vga
    00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
    Thanks in advance.

    cocotero wrote:Yes, KMS is enabled. I've read  that the better solution is to downgrade some xorg related packages. Is it impossible to use intel driver on 3 or more years old laptops? I mean, with good performance.
    Unfortunately  yes, I have seen since I use linux (like five years) that once a intel video card is not supported any more there is no going back to its optimum state, also the problem with downgrading packages is that at some point you would not be able to update other software any more with out issues.

  • Poor print performance with Adobe Reader 11.0.06 on XenApp 6.5/Windows Server 2008 R2 SP1

    Hi community,
    here are informations to our environment:
    Windows Server 2008 R2 with SP1 - mspatchlevel 05/2014
    XenApp 6.5 RP3 + Hotfix_XA650R01W2K8R2X64003 + Hotfix_XA650R03W2K8R2X64013
    AcroRead.msi + 11001.msp + 11003.msp + 11004.msp + 11006.msp
    Network: 10GB
    Problem:
    After migration to Adobe Reader 11.0.06 our users are complain about long printingtimes with PDF documents.
    What i have done:
    Test printing two different documents from local storage an network (dfs,nfs) - notice the printingtime in our environment depends not on used storage!
    1. 310 pages document with text (7,023KB)
    Adobe Acrobat XI on Samsung ML-451x 501x Series driver Version 3.11.39.00.58.01
    Average 52 seconds (done 5 same printjobs with same dokument) to print document in spooler.
    Change printer to:
    Adobe Acrobat XI on Samsung CLP-770 Series PCL6 Version 3.10.57:76
    Average 46 seconds (done 5 same printjobs with same dokument) to print document in spooler.
    2. 4 pages document with grafics (4,438KB)
    Adobe Acrobat XI on Samsung ML-451x 501x Series driver Version 3.11.39.00.58.01
    Average 45 seconds (done 5 same printjobs with same dokument) to print document in spooler.
    Change printer to:
    Adobe Acrobat XI on Samsung CLP-770 Series PCL6 Version 3.10.57:76
    Average 39 seconds (done 5 same printjobs with same dokument) to print document in spooler.
    Befor migration we have Server 2003 SP2 and XenApp 4.5FR6 with Adobe Reader 9.5.5
    I did the same testing but the time to print was much faster!
    1. 15 Seconds to print 310 pages document
    2. 28 seconds to print 4 pages document with grafics
    Any ideas to make printing faster on WindowsServer 2008R2 with Adobe Reader?
    Next step is testing the old version from reader on 2008R2 but on security aspects is this not the way...
    Thx
    Thomas

    Hi Pat,
    thx for your answer :-)
    i will try the older one 9.5.5 and the newest 11.0.07
    Regards,
    Thomas

  • Poor query performance with BETWEEN

    I'm using Oracle Reports 6i.
    I needed to add Date range parameters (Starting and Ending dates) to a report. I used lexicals in the Where condition to handle the logic.
    If no dates given,
    Start_LEX := '/**/' and
    End_LEX := '/**/'
    If Start_date given,
    Start_LEX := 'AND t1.date >= :Start_date'
    If End_date given,
    End_LEX := 'AND t1.date <= :End_date'
    When I run the report with no dates or only one of the dates, it finishes in 3 to 8 seconds.
    But when I supply both dates, it takes > 5 minutes.
    So I did the following
    If both dates are given and Start_date = End date,
    Start_LEX := 'AND t1.date = :Start_date'
    End_LEX := '/**/'
    This got the response back to the 3 - 8 second range.
    I then tried this
    if both dates are given and Start_date != End date,
    Start_LEX := 'AND t1.date BETWEEN :Start_date AND :End_date'
    End_LEX := '/**/'
    This didn't help. The response was still in the 5+ minutes range.
    If I run the query outside of Oracle Reports, in PL/SQL Developer or SQLplus, it returns the same data in 3 - 8 seconds in all cases.
    Does anyone know what is going on in Oracle Reports when a date is compared with two values either separately or with a BETWEEN? Why does the query take approx. 60 times as long to execute?

    Hi,
    Observe access plan first by using BETWEEN as well as using <= >=.
    Try to impose logic of using NVL while forming lexical parameters.
    Adinath Kamode

Maybe you are looking for

  • Windows Deployment Services and Surface Pro 2

    The issue I am seeing is when trying load the Windows Boot Manager, before selecting a boot image. The boot manager is loading in the lower 1/4 of the screen. It will not move past this loading screen and seeing how it is not displaying correctly, I

  • Printing with Adobe Acrobat 9 Standard

    Does anyone have issues printing in Adobe Acrobat 9 Standard with the HP CM1415fnw? I thought I have the latest driver downloaded.

  • Need help with Submit button

    I'm needing a script that locks all of the fields once the submit button is pressed and it's emailed to someone else. Is that possible? Thanks in advance for your help.

  • Using EJB vs Socket : expensive satellite line

    We are migrating a bank system from Clipper to Java(J2EE). One of the requisites is to save the bandwidth through the satellite line. Some developers came with a idea to make an object in bank store that talks with the central server through sockets,

  • How to solve the error -1?

    I tried to export mi project as a master file, but the program gave me this error -1, saying that there was a problem creating frame 696. I tryed to export the project as an apple device format and it gave me the error -50. Does anyone knows how to s