How to isolate poor performance caused by NETWORK

Hi Friends,
I would like to know a way to isolate sql server bad query performance is caused by NETWORK and not the sql server.
Are there any specific tips and tricks in ssms, waitype of specific perfmon counter permissable values for network is concerned? How to baseline the network related counters and what values should I consider as good /better/poor.
Any help would be appreciated.
Thank you.

You need to talk to the network manager about testing network performance.
Related blog: "As you may already be aware, the ASYNC_NETWORK_IO (seen in SQL 2005) and NETWORKIO (seen in SQL 2000) wait types are associated with either a calling application that is not processing results quickly enough from SQL
Server or is associated with a network performance issue."
LINK:
http://blogs.msdn.com/b/joesack/archive/2009/01/09/troubleshooting-async-network-io-networkio.aspx
ASYNCH_NETWORK_IO wiki:
http://mssqlwiki.com/sqlwiki/sql-performance/async_network_io-or-network_io/
Kalman Toth Database & OLAP Architect
IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Similar Messages

  • Poor performance caused by using OCI driver?

    [Sorry for the multipost]
    I'm working on a medium-sized Apache / Tomcat / WLS 5.10 / Oracle
    system hosted on some 4-processor Suns. The Apache / Tomcat tier
    uses one box, the WebLogic tier uses another, and the Oracle tier
    uses a third.
    We've found that the performance, measured as the time it takes user
    operations like loading a page that displays database data, gets
    unacceptably bad at suspiciously low loads. When the system is in
    this state, none of the machines appears to be pushed very hard.
    There's no significant paging going on, the disk and network I/O
    isn't out of line, and the CPU load just isn't high enough to
    explain what's going on. Only the WebLogic tier shows a load over
    10%. When the system is perceived as too slow by the users, the
    CPU load on this tier is only 30-40%.
    To try to find out what's going on, I did a series of thread dumps.
    When the system is heavily loaded, I only see about three Oracle
    statements currently being processed (runnable threads with call
    stacks inside weblogic.db.oci.*). What I do see lots of is blocked
    (and one runnable) threads inside
    weblogic.rjvm.RJVMImpl.removePeerGoneListener or
    weblogic.rjvm.RJVMImpl.addPeerGoneListener. These threads appear to
    be attempting to obtain or release database connections.
    I don't know why, but the site is configured to use the WebLogic OCI
    driver for Oracle, instead of the Oracle-supplied thin driver. Is what I'm
    seeing what Sun is describing in this paragraph
    (excerpted from http://java.sun.com/docs/hotspot/PerformanceFAQ.html#24):
    Oracle provides two types of database drivers: a type-2
    driver, called the OCI (Oracle Call Interface) driver
    that utilizes native code, and a type-4 pure Java driver
    called the thin driver. In single processor environments,
    the thin driver works somewhat better than the OCI driver
    because of the JNI overhead associated with the OCI
    driver. On multi-processor configuations, synchronization
    points within Solaris used by the OCI driver become big
    bottlenecks and prevent scaling. We recommend using the
    thin driver in all cases.
    -- Erik

    Hi. I'll chip in here too. Yes, you are wasting JVM cycles having all those
    wasted threads. Threads aren't free, inexhaustable sources of compute power
    that some people assume (I'm not saying you're one). All these threads do
    share a single OS process and CPU. The JVM has to check all these all the
    time to see if they have something to do. I recommend configuring the
    server to run about 15 or 20 execute-threads.
    I see only one thread waiting on Oracle to return data, so I don't think this
    is a JDBC issue necessarily. What I do see is lots of threads trying to operate
    on a Vector, all being blocked, or at least serialized by the lock this thread has, below.
    Is the server hung at this point, or just slow?
    "ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
    at java.util.Vector.removeElementAt(Vector.java:509)
    at java.util.Vector.removeElement(Vector.java:598)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
    at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
    at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
    at
    com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
    at
    weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at
    weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Erik Horstkotte wrote:
    "Rob Woollen" <[email protected]> wrote in message
    news:[email protected]...
    You generally need a lot of data to find the performance problem in
    a distributed system like this.Understood, but I was hoping that someone would recognize my description
    as the "signature" of the locking problem with the OCI driver that Sun
    describes.
    It's very easy to switch to the Thin driver so you might as well
    try it.I had hoped so, and in most cases, you're likely correct. Unfortunately,
    the OCI driver is a touch more permissive than the thin driver. Some
    errors (too many bind parameters) have crept in to our code that don't
    cause problems for the OCI driver, but cause exceptions to be thrown by
    the thin driver. In this particular case, I'm trying to solve a problem on
    a production system - fixing the code there isn't an option (we are
    switching to thin driver in our next release, so we are fixing these
    problems).
    If that doesn't help, I would suggest inserting some timing logic
    in your code. In particular, I'd want to know the time a request
    entered apache/tomcat, left apache/tomcat, entered WLS, left WLS
    (to go to the database), returned from the database, left WLS, got
    back to apache/tomcat, and finally left apache/tomcat to return the
    response. With information like that, you should be able to narrow
    down the problem a bit.In the next release, this is a good idea, and we'll probably do something
    much like this. Unfortunately I can't make changes to the code on the
    production site, so I have to rely on more passive methods of data
    collection for the moment.
    "Slava Imeshev" <[email protected]> wrote in message
    news:[email protected]...
    There can be other reasons for bad performance ranging from
    serialized access to singletons to inefficient queries to
    server mis-configuration. I have some doubts that oci driver
    would affect performance at low loads.I don't see any evidence of serialization blocking, except for the
    interesting locking issue that I mentioned in the original message (a
    PeerGoneListener table maintained somewhere down inside WLS).
    I'm certain that inefficient queries play a large role in our
    performance problems.
    Service mis-configuration could very well play a role here. Note for
    example the large number of blocked idle execute threads in the thread
    dump below. Clearly this instance has way too many execute threads. Not
    knowing the internal architecture of WebLogic Server, nor the
    implementation method Sun used for monitors in Solaris JVM 1.4.2, I don't
    know how much of an impact an excess of execute threads has on
    performance. Anyone?
    Could you post a questionable thread dump here?See the bottom of this message. The dump has been "blinded" to remove some
    customer-specific information.
    Also, what's the load in terms of number of concurrent users
    and requests per second?At peak load, there are about 60 users logged in, of whom only about 4-12
    actually do much. The number of requests per second is very peaky, and
    varies from about 1-10 per second. The complexity of requests also varies
    wildly.
    I've attached a thread dump from a point in time when the WebLogic Server
    instance was taking about 30% of the CPU.
    Any and all ideas are appreciated.
    -- Erik
    Full thread dump:
    "HighPriority TimeEventGenerator" daemon prio=9 tid=0x4223ed0 nid=0xa7 waiting on monitor [0xcceff000..0xcceffc68]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:141)
    at java.lang.Thread.run(Thread.java:484)
    "ListenThread" prio=5 tid=0x423f7a0 nid=0xa6 runnable [0xccbff000..0xccbffc68]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:325)
    "NBExecuteThread-1" daemon prio=5 tid=0x331ea0 nid=0xa2 waiting on monitor [0xccfff000..0xccfffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "NBExecuteThread-0" daemon prio=5 tid=0x3317b8 nid=0xa1 waiting on monitor [0xcd0ff000..0xcd0ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-149" daemon prio=5 tid=0x330228 nid=0xa0 runnable [0xcd1ff000..0xcd1ffc68]
    at weblogic.socket.PosixSocketMuxer.poll(Native Method)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:290)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-148" daemon prio=5 tid=0x32f740 nid=0x9f waiting on monitor [0xcd2ff000..0xcd2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-147" daemon prio=5 tid=0x32ec58 nid=0x9e waiting for monitor entry [0xcd3ff000..0xcd3ffc68]
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-146" daemon prio=5 tid=0x32e170 nid=0x9d waiting for monitor entry [0xcd4ff000..0xcd4ffc68]
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:289)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-145" daemon prio=5 tid=0x32ce80 nid=0x9c waiting on monitor [0xcd5ff000..0xcd5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-144" daemon prio=5 tid=0x32c398 nid=0x9b waiting for monitor entry [0xcd6ff000..0xcd6ffc68]
    at java.util.Vector.removeElement(Vector.java:595)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.jts.internal.CoordinatorImpl.unregisterClientDeathNotification(CoordinatorImpl.java:101)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:347)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.ProfileSessionEJBEOImpl.getContactNumbers(ProfileSessionEJBEOImpl.java:5687)
    at com.xxx.yyy.as.ProfileSessionEJBEOImpl_WLSkel.invoke(ProfileSessionEJBEOImpl_WLSkel.java:222)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-143" daemon prio=5 tid=0x32b8b0 nid=0x9a waiting on monitor [0xcd7ff000..0xcd7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-142" daemon prio=5 tid=0x32adc8 nid=0x99 waiting on monitor [0xcd8ff000..0xcd8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-141" daemon prio=5 tid=0x32a2e0 nid=0x98 waiting on monitor [0xcd9ff000..0xcd9ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-140" daemon prio=5 tid=0x3297f8 nid=0x97 waiting on monitor [0xcdaff000..0xcdaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-139" daemon prio=5 tid=0x328d10 nid=0x96 waiting for monitor entry [0xcdbff000..0xcdbffc68]
    at java.util.Vector.addElement(Vector.java:573)
    at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
    at weblogic.time.server.ScheduledTrigger.setExecCon(ScheduledTrigger.java:46)
    at weblogic.t3.srvr.T3ServerServices.getScheduledTrigger(T3ServerServices.java:177)
    at weblogic.jts.internal.CoordinatorImpl.resetTimer(CoordinatorImpl.java:210)
    at weblogic.jts.internal.CoordinatorImpl.<init>(CoordinatorImpl.java:83)
    at weblogic.jts.internal.CoordinatorFactoryImpl.createCoordinator(CoordinatorFactoryImpl.java:95)
    at weblogic.jts.internal.CoordinatorFactoryImpl_ServiceStub.createCoordinator(CoordinatorFactoryImpl_ServiceStub.java:69)
    at weblogic.jts.internal.TxContext.getCoordinator(TxContext.java:139)
    at weblogic.jts.internal.TxContext.begin(TxContext.java:93)
    at weblogic.jts.internal.CurrentImpl.begin(CurrentImpl.java:48)
    at weblogic.jts.internal.TransactionManagerImpl.begin(TransactionManagerImpl.java:56)
    at weblogic.ejb.internal.EJBHomeImpl.setupTransaction(EJBHomeImpl.java:838)
    at weblogic.ejb.internal.BaseEJBObject.setupTransaction(BaseEJBObject.java:281)
    at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:471)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfigurationSiteSpecific(SecuritySessionEJBEOImpl.java:143)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:254)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-138" daemon prio=5 tid=0x328228 nid=0x95 waiting on monitor [0xcdcff000..0xcdcffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-137" daemon prio=5 tid=0x326d38 nid=0x94 waiting on monitor [0xcddff000..0xcddffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-136" daemon prio=5 tid=0x326250 nid=0x93 waiting on monitor [0xcdeff000..0xcdeffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-135" daemon prio=5 tid=0x325768 nid=0x92 waiting on monitor [0xcdfff000..0xcdfffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-134" daemon prio=5 tid=0x324c80 nid=0x91 waiting on monitor [0xce0ff000..0xce0ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-133" daemon prio=5 tid=0x324198 nid=0x90 waiting on monitor [0xce1ff000..0xce1ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-132" daemon prio=5 tid=0x3236b0 nid=0x8f waiting on monitor [0xce2ff000..0xce2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-131" daemon prio=5 tid=0x322bc8 nid=0x8e waiting on monitor [0xce3ff000..0xce3ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-130" daemon prio=5 tid=0x3220e0 nid=0x8d waiting on monitor [0xce4ff000..0xce4ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-129" daemon prio=5 tid=0x3215f8 nid=0x8c waiting on monitor [0xce5ff000..0xce5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-128" daemon prio=5 tid=0x320b10 nid=0x8b waiting on monitor [0xce6ff000..0xce6ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-127" daemon prio=5 tid=0x320028 nid=0x8a waiting on monitor [0xce7ff000..0xce7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-126" daemon prio=5 tid=0x31f540 nid=0x89 waiting on monitor [0xce8ff000..0xce8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-125" daemon prio=5 tid=0x31ea58 nid=0x88 waiting on monitor [0xce9ff000..0xce9ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-124" daemon prio=5 tid=0x31df70 nid=0x87 waiting on monitor [0xceaff000..0xceaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-123" daemon prio=5 tid=0x31d488 nid=0x86 waiting on monitor [0xcebff000..0xcebffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-122" daemon prio=5 tid=0x31bb90 nid=0x85 waiting on monitor [0xcecff000..0xcecffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-121" daemon prio=5 tid=0x31b0a8 nid=0x84 waiting on monitor [0xcedff000..0xcedffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-120" daemon prio=5 tid=0x31a5c0 nid=0x83 waiting for monitor entry [0xceeff000..0xceeffc68]
    at java.util.Vector.addElement(Vector.java:573)
    at weblogic.rjvm.RJVMImpl.addPeerGoneListener(RJVMImpl.java:348)
    at weblogic.jdbc20.rmi.internal.ConnectionImpl.<init>(ConnectionImpl.java:39)
    at weblogic.jdbc20.common.internal.RmiDataSource.getConnection(RmiDataSource.java:65)
    at weblogic.jdbc20.common.internal.RmiDataSource_ServiceStub.getConnection(RmiDataSource_ServiceStub.java:179)
    at com.xxx.yyy.asutil.DataAccessManager.getConnection(DataAccessManager.java:113)
    at com.xxx.yyy.as.MetricsSessionEJB.logEvent(MetricsSessionEJB.java:222)
    at com.xxx.yyy.as.MetricsSessionEJBEOImpl.logEvent(MetricsSessionEJBEOImpl.java:324)
    at com.xxx.yyy.as.MetricsSessionEJBEOImpl_WLSkel.invoke(MetricsSessionEJBEOImpl_WLSkel.java:242)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-119" daemon prio=5 tid=0x319ad8 nid=0x82 waiting on monitor [0xcefff000..0xcefffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-118" daemon prio=5 tid=0x318ff0 nid=0x81 runnable [0xcf0fe000..0xcf0ffc68]
    at weblogic.db.oci.OciCursor.execAndFetch(Native Method)
    at weblogic.db.oci.OciCursor.oci_execAndFetch(OciCursor.java:1890)
    at weblogic.jdbcbase.oci.Statement.executeQuery(Statement.java:905)
    at weblogic.jdbcbase.jts.Statement.executeQuery(Statement.java:58)
    at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:46)
    at weblogic.jdbc20.rmi.SerialPreparedStatement.executeQuery(SerialPreparedStatement.java:40)
    at com.xxx.yyy.as.SecuritySessionEJB.getClientConfiguration(SecuritySessionEJB.java:1669)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl.getClientConfiguration(SecuritySessionEJBEOImpl.java:985)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLSkel.invoke(SecuritySessionEJBEOImpl_WLSkel.java:234)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.extensions.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:82)
    at weblogic.rmi.internal.ServerRequest.sendOneWay(ServerRequest.java:73)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:77)
    at com.xxx.yyy.as.SecuritySessionEJBEOImpl_WLStub.getClientConfiguration(SecuritySessionEJBEOImpl_WLStub.java:703)
    at com.xxx.yyy.as.QuestionnaireSessionEJB.getQuestionnaireBatches(QuestionnaireSessionEJB.java:3479)
    at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl.getQuestionnaireBatches(QuestionnaireSessionEJBEOImpl.java:631)
    at com.xxx.yyy.as.QuestionnaireSessionEJBEOImpl_WLSkel.invoke(QuestionnaireSessionEJBEOImpl_WLSkel.java:237)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-117" daemon prio=5 tid=0x317f00 nid=0x80 waiting on monitor [0xcf1ff000..0xcf1ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-116" daemon prio=5 tid=0x317418 nid=0x7f waiting on monitor [0xcf2ff000..0xcf2ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-115" daemon prio=5 tid=0x316930 nid=0x7e waiting on monitor [0xcf3ff000..0xcf3ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-114" daemon prio=5 tid=0x315e48 nid=0x7d waiting on monitor [0xcf4ff000..0xcf4ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-113" daemon prio=5 tid=0x314b58 nid=0x7c waiting on monitor [0xcf5ff000..0xcf5ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-112" daemon prio=5 tid=0x314070 nid=0x7b waiting on monitor [0xcf6ff000..0xcf6ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-111" daemon prio=5 tid=0x313588 nid=0x7a waiting on monitor [0xcf7ff000..0xcf7ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-110" daemon prio=5 tid=0x312aa0 nid=0x79 waiting on monitor [0xcf8ff000..0xcf8ffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-109" daemon prio=5 tid=0x311fb8 nid=0x78 runnable [0xcf9ff000..0xcf9ffc68]
    at java.util.Vector.removeElementAt(Vector.java:509)
    at java.util.Vector.removeElement(Vector.java:598)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.time.server.ScheduledTrigger.destroy(ScheduledTrigger.java:112)
    at weblogic.time.server.ScheduledTrigger.cancel(ScheduledTrigger.java:100)
    at weblogic.jts.internal.CoordinatorImpl.cancelCurrentTimer(CoordinatorImpl.java:199)
    at weblogic.jts.internal.CoordinatorImpl.commit(CoordinatorImpl.java:404)
    at weblogic.jts.internal.TxContext.commit(TxContext.java:255)
    at weblogic.ejb.internal.StatelessEJBObject.postInvokeOurTx(StatelessEJBObject.java:103)
    at weblogic.ejb.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:849)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl.findTaskByFilter(TaskSessionEJBEOImpl.java:784)
    at com.xxx.yyy.as.TaskSessionEJBEOImpl_WLSkel.invoke(TaskSessionEJBEOImpl_WLSkel.java:101)
    at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
    at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    "ExecuteThread-108" daemon prio=5 tid=0x3114d0 nid=0x77 waiting on monitor [0xcfaff000..0xcfaffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-107" daemon prio=5 tid=0x3109e8 nid=0x76 waiting on monitor [0xcfbff000..0xcfbffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-106" daemon prio=5 tid=0x30ff00 nid=0x75 waiting on monitor [0xcfcff000..0xcfcffc68]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
    "ExecuteThread-105" daemon prio=5 tid=0x30f418 nid=0x74 waiting for monitor entry [0xcfdff000..0xcfdffc68]
    at java.util.Vector.removeElement(Vector.java:595)
    at weblogic.rjvm.RJVMImpl.removePeerGoneListener(RJVMImpl.java:352)
    at weblogic.jdbc20.rmi.internal.ConnectionImpl.close(ConnectionImpl.java:161)
    at weblogic.jdbc20.rmi.SerialConnection.close(SerialConnection.java:162)
    at com.xxx.yyy.asutil.Util

  • How to design to perform for a network mediation correlation application?

    we have three network devices, each producing text based logs for their own activity. each node can start a traffic and each node can be an end. but a traffic here can mean going back and forward on nodes. and we are intrested to report the each traffics start end nodes, like a CDR we may say.
    I have imported the data of each node to a table, but this is not mandatory, in order to have the required output I can easily denormalize the target tables, similar to a ETL of a DW.
    If I have the data in three seperate tables I suppose I will need to implement a recursive pl/sql function, since the data is ~250 million rows per day to have a performant process to find the start and end points of each traffic what kind of a table design and as a result SQL or PL/SQL algoritm do you advise?
    any example code you may be aware of pipelined pl/sql feature used recursively?
    thank you.
    ps: for the current test environment we have 10.2 installed on solaris but we can easily decide to use 11.1 if there is any special motivation for this need.

    You could dig through the docs and try to figure out the file format manually, or you could do this the easy way.  Simply use the Outline Load Utility to export your attribute dimension from Planning.  The export file format is the same as the import file format.  You might have to manually add a couple of test members to your attribute dimension so that your export file has some content.  Then simply update the file you exported, and import it.
    (I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
    Hope this helps,
    - Jake

  • Poor Performance over Converged Networks using LBFO Team

    Hi,
    I have  built a Hyper-v 2012 R2 cluster with converged networking and correct logical networks. 
    However, I notice that I am not able to utilise more than apprx 1gb over the converged network for live migration, cluster, management etc even though they have a total of 8 x 1gb physical adapters available (switch independant, dynamic load balancing).
    e.g
    Hyper-v host1 and hyper-v host2 have 4 x 1gb pNics connected to switch1 and 4x1gb pNics connected to switch2. Switch1 and switch2 has a portchannel configured between them.
    I can see if I carry out a file copy between Hyper-v host1 and Hyper-v host2 (both configured exactly the same) then the Management, Live-Migration and Cluster vNics on the host use approx 300mbps on each vNic during the copy but never get anywhere near
    their full utilization (here I would be expecting to see approximately the total of the team available bandwidth which is 8gbps as there is no other traffic using these networks).
    Is it because the host vNICs cannot use vRSS (VMQ)? Although I struggle to see this as the issue because I don't see any CPU cores maxing out during the copy! Or maybe someone could recommend anything else to check?
    Microsoft Partner

    Without doing a case study on your environment, it would be pretty much impossible to give you a truly correct answer on what you should do.
    In the generic sense, using at least partial convergence is usually in your best interests. If you have a completely unconverged environment, then it is absolutely guaranteed that any given adapter will only have a single gigabit pipe to work with no matter
    what. Aidan's example of dual concurrent Live Migrations is good, but it's only one of a nearly infinite set of possibilities. As another example, let's say that you start a hypervisor-level over-the-network backup and at the same time you copy an ISO file
    from a remote file server into the management operating system. In an unconverged network, they'll both be fighting for attention from one adapter. If you have 8 total adapters, you can almost guarantee that at least one of the other 7 is sitting idle -- and
    there's nothing you can do about it.
    If you're converged (dependent upon setup), then you have a pretty good chance that those activities will be separated across physical adapters. Extrapolate those examples to the management OS and a stack of virtual machines, all cumulatively involved in
    dozens or hundreds of individual transmissions, and you see pretty quickly that convergence gives you the greatest capability for utilization of available resources. It's like when the world went from single- to dual-core computers. A dual-core system isn't
    twice as fast as its single-core counterpart. Its operating system's thread scheduler just has two places to run threads instead of one. But, the rule of one thread per core still applies. The name of the game is concurrency, not aggregation.
    Again, that's in the generic sense. When you get into trying to tap the power of SMB Multichannel, that changes the equation. That's where the case study picks up.
    Eric Siron Altaro Hyper-V Blog
    I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
    "Every relationship you have is in worse shape than you think."

  • General poor performance of my Mac mini

    I have been using my mac mini for over a year, it continues to frustrate me how slow and unresponsive it can be even though I do very little with it, i.e organise photos and browse the web - usually looking for solutions to the poor performance problem!
    I came a cross this app that has given me lots of information, unfortunately with my limited IT know-how there is nothing here that gives me any clues, as to the cause of the problem. I guess the red font is not good?
    I'm sorry i can't be more specific about the problem other than to say that iPhoto and Safari the two programmes i use way more often than any other, keep giving me the beach ball. My internet speed is ok 25 Mbps down - 4.5 Mbps
    Is there anything here that stands out as being wrong? if so any suggestions/ instructions for what I should do?
    p.s. i had to quit Safari while writing this and have a report for this if it helps?
    Any help much appreciated.
    Problem description:
    My mac is just generally very slow. I only use it to look at the internet and manage photos.
    EtreCheck version: 2.1.5 (108)
    Report generated 3 January 2015 16:03:59 GMT
    Click the [Support] links for help with non-Apple products.
    Click the [Details] links for more information about that line.
    Click the [Adware] links for help removing adware.
    Hardware Information: ℹ️
      Mac mini (Late 2012) (Verified)
      Mac mini - model: Macmini6,2
      1 2.3 GHz Intel Core i7 CPU: 4-core
      4 GB RAM Upgradeable
      BANK 0/DIMM0
      2 GB DDR3 1600 MHz ok
      BANK 1/DIMM0
      2 GB DDR3 1600 MHz ok
      Bluetooth: Good - Handoff/Airdrop2 supported
      Wireless:  en1: 802.11 a/b/g/n
    Video Information: ℹ️
      Intel HD Graphics 4000
      DELL U2412M 1920 x 1200
    System Software: ℹ️
      OS X 10.10.1 (14B25) - Uptime: 5 days 22:14:3
    Disk Information: ℹ️
      APPLE HDD HTS541010A9E662 disk0 : (1 TB)
      EFI (disk0s1) <not mounted> : 210 MB
      Macintosh HD (disk0s2) / : 999.35 GB (759.01 GB free)
      Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
    USB Information: ℹ️
      HP Photosmart B110 series
      Apple Inc. BRCM20702 Hub
      Apple Inc. Bluetooth USB Host Controller
      Apple, Inc. IR Receiver
    Thunderbolt Information: ℹ️
      Apple Inc. thunderbolt_bus
    Gatekeeper: ℹ️
      Mac App Store and identified developers
    Problem System Launch Daemons: ℹ️
      [killed] com.apple.AssetCacheLocatorService.plist
      [killed] com.apple.coreservices.appleid.passwordcheck.plist
      [killed] com.apple.ctkd.plist
      [killed] com.apple.wdhelper.plist
      [killed] com.apple.xpc.smd.plist
      5 processes killed due to memory pressure
    Launch Daemons: ℹ️
      [loaded] com.adobe.fpsaud.plist [Support]
    User Login Items: ℹ️
      iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
      Dropbox Application (/Applications/Dropbox.app)
      Wondershare Helper Compact Application (/Users/[redacted]/Library/Application Support/Helper/Wondershare Helper Compact.app)
    Internet Plug-ins: ℹ️
      Silverlight: Version: 5.1.30514.0 - SDK 10.6 [Support]
      FlashPlayer-10.6: Version: 16.0.0.235 - SDK 10.6 [Support]
      Flash Player: Version: 16.0.0.235 - SDK 10.6 [Support]
      QuickTime Plugin: Version: 7.7.3
      Unity Web Player: Version: UnityPlayer version 4.5.5f1 - SDK 10.6 [Support]
      Default Browser: Version: 600 - SDK 10.10
    3rd Party Preference Panes: ℹ️
      Flash Player  [Support]
    Time Machine: ℹ️
      Auto backup: YES
      Volumes being backed up:
      Macintosh HD: Disk size: 999.35 GB Disk used: 240.33 GB
      Destinations:
      Time Capsule [Network]
      Total size: 2.00 TB
      Total number of backups: 56
      Oldest backup: 2014-09-30 04:29:13 +0000
      Last backup: 2015-01-03 15:37:35 +0000
      Size of backup disk: Adequate
      Backup size 2.00 TB > (Disk used 240.33 GB X 3)
    Top Processes by CPU: ℹ️
        110% com.apple.WebKit.Plugin.64
          6% WindowServer
          1% Activity Monitor
          1% coreaudiod
          1% sysmond
    Top Processes by Memory: ℹ️
      1.11 GB com.apple.WebKit.Plugin.64
      73 MB iTunes
      49 MB com.apple.WebKit.WebContent
      39 MB mds
      39 MB WindowServer
    Virtual Memory Information: ℹ️
      68 MB Free RAM
      1.07 GB Active RAM
      1.02 GB Inactive RAM
      893 MB Wired RAM
      63.93 GB Page-ins
      2.15 GB Page-outs
    Diagnostics Information: ℹ️
      Jan 1, 2015, 11:43:39 AM /Library/Logs/DiagnosticReports/com.apple.WebKit.Plugin.64_2015-01-01-114339_[r edacted].cpu_resource.diag [Details]
      Jan 1, 2015, 11:32:46 AM /Library/Logs/DiagnosticReports/WindowServer_2015-01-01-113246_[redacted].crash
      Jan 1, 2015, 11:00:30 AM /Library/Logs/DiagnosticReports/com.apple.WebKit.Plugin.64_2015-01-01-110030_[r edacted].cpu_resource.diag [Details]
      Jan 1, 2015, 10:19:03 AM /Library/Logs/DiagnosticReports/iBooks_2015-01-01-101903_[redacted].cpu_resourc e.diag [Details]

    Hi Linc Davis
    Thank you for taking the time to respond.
    I got this information from a time when I was opening up iPhoto, and then going to the iCloud folder. To be honest it wasn't the most disastrous of events, I did get a few beachballs and when I opened up a shared folder the photos weren't loaded as normal. As I get more lengthy delays in carrying out any activities I will post back the console results.
    Just as a bit more info, I don't consider my problem an update to Yosemite problem, if anything since updating performance has been improved from Mavericks.
    Do you have any comments about upgrading RAM from the 4GB I have?
    Should I act on any of the messages in red from the EtreCheck report?
    Many Thanks
    Duncan
    03/01/2015 19:30:18.331 com.apple.iCloudHelper[12481]: objc[12481]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
    03/01/2015 19:30:18.391 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    03/01/2015 19:30:19.162 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:30:19.162 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:30:19.163 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:30:19.163 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:30:19.186 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:30:19.187 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:30:19.188 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:30:19.188 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:30:19.188 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:30:19.188 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:30:25.446 WindowServer[7810]: common_reenable_update: UI updates were finally reenabled by application "iPhoto" after 10.70 seconds (server forcibly re-enabled them after 1.00 seconds)
    03/01/2015 19:30:33.548 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:30:33.919 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:30:34.077 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:30:34.605 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:30:34.774 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:30:34.853 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:30:47.562 pkd[12123]: FCIsAppAllowedToLaunchExt [343] -- *** _FCMIGAppCanLaunch timed out. Returning false.
    03/01/2015 19:31:10.695 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:31:10.807 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:31:16.961 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:31:18.514 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:31:18.593 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:31:22.538 discoveryd[49]: Basic Sockets SetDelegatePID() failed for PID[3491] errno[3] result[-1]
    03/01/2015 19:31:27.912 mds[32]: (DiskStore.Normal:2376) 6052001 1.780097
    03/01/2015 19:31:56.831 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:31:57.224 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:31:57.281 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:31:57.405 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:31:58.507 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:31:58.541 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:31:59.160 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:32:09.891 com.apple.InputMethodKit.UserDictionary[12456]: -[PFUbiquitySetupAssistant canReadFromUbiquityRootLocation:](1492): CoreData: Ubiquity:  Error attempting to read ubiquity root url: file:///Users/Duncan/Library/Mobile%20Documents/com~apple~TextInput/Dictionarie s/.
    Error: Error Domain=NSCocoaErrorDomain Code=134323 "The operation couldn’t be completed. (Cocoa error 134323.)" UserInfo=0x7f90e152a380 {NSAffectedObjectsErrorKey=<PFUbiquityLocation: 0x7f90e152a2e0>: /Users/Duncan/Library/Mobile Documents/com~apple~TextInput}
    userInfo: {
        NSAffectedObjectsErrorKey = "<PFUbiquityLocation: 0x7f90e152a2e0>: /Users/Duncan/Library/Mobile Documents/com~apple~TextInput";
    03/01/2015 19:32:12.862 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:32:20.818 com.apple.SecurityServer[53]: Killing auth hosts
    03/01/2015 19:32:20.819 com.apple.SecurityServer[53]: Session 100281 destroyed
    03/01/2015 19:32:20.974 com.apple.SecurityServer[53]: Session 100577 created
    03/01/2015 19:32:34.833 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:32:35.767 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:32:35.789 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:32:35.980 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:32:36.273 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:32:36.487 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:32:47.035 WindowServer[7810]: disable_update_timeout: UI updates were forcibly disabled by application "iPhoto" for over 1.00 seconds. Server has re-enabled them.
    03/01/2015 19:32:50.555 WindowServer[7810]: common_reenable_update: UI updates were finally reenabled by application "iPhoto" after 4.52 seconds (server forcibly re-enabled them after 1.00 seconds)
    03/01/2015 19:32:51.578 WindowServer[7810]: disable_update_timeout: UI updates were forcibly disabled by application "iPhoto" for over 1.00 seconds. Server has re-enabled them.
    03/01/2015 19:32:52.745 WindowServer[7810]: common_reenable_update: UI updates were finally reenabled by application "iPhoto" after 2.17 seconds (server forcibly re-enabled them after 1.00 seconds)
    03/01/2015 19:32:53.098 mds[32]: (DiskStore.Normal:2376) 6052001 1.279589
    03/01/2015 19:33:03.332 BezelServices 245.23[7816]: ASSERTION FAILED: dvcAddrRef != ((void *)0) -[DriverServices getDeviceAddress:] line: 2602
    03/01/2015 19:33:03.332 BezelServices 245.23[7816]: ASSERTION FAILED: dvcAddrRef != ((void *)0) -[DriverServices getDeviceAddress:] line: 2602
    03/01/2015 19:33:11.961 mds[32]: (DiskStore.Normal:2376) 6052001 1.939804
    03/01/2015 19:33:29.541 WindowServer[7810]: disable_update_timeout: UI updates were forcibly disabled by application "iPhoto" for over 1.00 seconds. Server has re-enabled them.
    03/01/2015 19:33:32.354 WindowServer[7810]: common_reenable_update: UI updates were finally reenabled by application "iPhoto" after 3.81 seconds (server forcibly re-enabled them after 1.00 seconds)
    03/01/2015 19:33:44.549 discoveryd[49]: Basic DNSResolver  dropping message because it doesn't match the one sent Port:53 MsgID:20602
    03/01/2015 19:33:54.055 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:34:05.143 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.143 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.165 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.165 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.165 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.166 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:05.499 discoveryd[49]: WCFNameResolvesToAddr: called
    03/01/2015 19:34:05.499 discoveryd[49]: WCFNameResolvesToAddr: entering
    03/01/2015 19:34:07.001 discoveryd[49]: Basic Sockets SetDelegatePID() failed for PID[3491] errno[3] result[-1]
    03/01/2015 19:34:13.809 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:34:13.821 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:34:14.124 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:34:14.766 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:34:14.867 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)
    03/01/2015 19:34:17.769 WindowServer[7810]: scrollPhase Ended (4), but previous was 4 (not Began)
    03/01/2015 19:34:18.186 WindowServer[7810]: scrollPhase MayBegin (128), but previous was 1 (not 0, Cancelled or End)
    03/01/2015 19:34:18.186 WindowServer[7810]: scrollPhase Began (1), but previous was 1 (not 0, MayBegin or End)

  • URGENT: Migrating from SQL to Oracle results in very poor performance!

    *** IMPORTANT, NEED YOUR HELP ***
    Dear, I have a banking business solution from Windows/SQL Server 2000 to Sun Solaris/ORACLE 10g migrated. In the test environment everything was working fine. On the production system we have very poor DB performance. About 100 times slower than SQL Server 2000!
    Environment at Customer Server Side:
    Hardware: SUN Fire 4 CPU's, OS: Solaris 5.8, DB Oracle 8 and 10
    Data Storage: Em2
    DB access thru OCCI [Environment:OBJECT, Connection Pool, Create Connection]
    Depending from older applications it's necessary to run ORACLE 8 as well on the same Server. Since we have running the new solution, which is using ORACLE 10, the listener for ORACLE 8 is frequently gone (or by someone killed?). The performance of the whole ORACLE 10 Environment is very poor. As a result of my analyse I figured out that the process to create a connection to the connection pool takes up to 14 seconds. Now I am wondering if it a problem to run different ORACLE versions on the same Server? The Customer has installed/created the new ORACLE 10 DB with the same user account (oracle) as the older version. To run the new solution we have to change the ORACLE environment settings manually. All hints/suggestions to solve this problem are welcome. Thanks in advance.
    Anton

    On the production system we have very poor DB performanceHave you identified the cause of the poor performance is not the queries and their plans being generated by the database?
    Do you know if some of the queries appear to take more time than what it used to be on old system? Did you analyze such queries to see what might be the problem?
    Are you running RBO or CBO?
    if stats are generated, how are they generated and how often?
    Did you see what autotrace and tkprof has to tell you about problem queries (if in fact such queries have been identified)?
    http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10752/sqltrace.htm#1052

  • Poor performance with Oracle Spatial when spatial query invoked remotely

    Is anyone aware of any problems with Oracle Spatial (10.2.0.4 with patches 6989483 and 7003151 on Red Hat Linux 4) which might explain why a spatial query (SDO_WITHIN_DISTANCE) would perform 20 times worse when it was invoked remotely from another computer (using SQLplus) vs. invoking the very same query from the database server itself (also using SQLplus)?
    Does Oracle Spatial have any known problems with servers which use SAN disk storage? That is the primary difference between a server in which I see this poor performance and another server where the performance is fine.
    Thank you in advance for any thoughts you might share.

    OK, that's clearer.
    Are you sure it is the SQL inside the procedure that is causing the problem? To check, try extracting the SQL from inside the procedure and run it in SQLPLUS with
    set autotrace on
    set timing on
    SELECT ....If the plans and performance are the same then it may be something inside the procedure itself.
    Have you profiled the procedure? Here is an example of how to do it:
    Prompt Firstly, create PL/SQL profiler table
    @$ORACLE_HOME/rdbms/admin/proftab.sql
    Prompt Secondly, use the profiler to gather stats on execution characteristics
    DECLARE
      l_run_num PLS_INTEGER := 1;
      l_max_num PLS_INTEGER := 1;
      v_geom    mdsys.sdo_geometry := mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(0,0,45,45,90,0,135,45,180,0,180,-45,45,-45,0,0));
    BEGIN
      dbms_output.put_line('Start Profiler Result = ' || DBMS_PROFILER.START_PROFILER(run_comment => 'PARALLEL PROFILE'));  -- The comment name can be anything: here it is related to the Parallel procedure I am testing.
      v_geom := Parallel(v_geom,10,0.05,1);  -- Put your procedure call here
      dbms_output.put_line('Stop Profiler Result = ' || DBMS_PROFILER.STOP_PROFILER );
    END;
    SHOW ERRORS
    Prompt Finally, report activity
    COLUMN runid FORMAT 99999
    COLUMN run_comment FORMAT A40
    SELECT runid || ',' || run_date || ',' || run_comment || ',' || run_total_time
      FROM plsql_profiler_runs
      ORDER BY runid;
    COLUMN runid       FORMAT 99999
    COLUMN unit_number FORMAT 99999
    COLUMN unit_type   FORMAT A20
    COLUMN unit_owner  FORMAT A20
    COLUMN text        FORMAT A100
    compute sum label 'Total_Time' of total_time on runid
    break on runid skip 1
    set linesize 200
    SELECT u.runid || ',' ||
           u.unit_name,
           d.line#,
           d.total_occur,
           d.total_time,
           text
    FROM   plsql_profiler_units u
           JOIN plsql_profiler_data d ON u.runid = d.runid
                                         AND
                                         u.unit_number = d.unit_number
           JOIN all_source als ON ( als.owner = 'CODESYS'
                                   AND als.type = u.unit_type
                                   AND als.name = u.unit_name
                                AND als.line = d.line# )
    WHERE  u.runid = (SELECT max(runid) FROM plsql_profiler_runs)
    ORDER BY d.total_time desc;Run the profiler in both environments and see if you can see where the slowdown exists.
    regards
    Simon

  • Poor Performance using Generic Conectivity for ODBC

    Hi my friends.
    I have a problem usign Generic Conectivity , I need update 500,000 records in MS SQL Server 2005, I'm using Generic Conectivity for ODBC. In my Oracle Database i have create a DB_LINK called TEST to redirect to MS SQL Server database.
    Oracle Database: 10.2.0.4
    MS SQL Server version: 2005
    The time for update 1,000 records in MS SQL Server using DBMS_HS_PASSTHROUGH is ten minutes. This is a poor performance.
    This is de PL/SQL
    DECLARE
    c INTEGER;
    nr INTEGER;
    CURSOR c_TEST
    IS
    SELECT "x", "y"
    FROM TEST_cab
    WHERE ROWNUM <= 1000
    ORDER BY "y";
    BEGIN
    FOR cur IN c_TEST
    LOOP
    c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@TEST;
    DBMS_HS_PASSTHROUGH.PARSE@TEST(
    c,
    'UPDATE sf_TEST_sql
    SET observation= ?
    WHERE department_id = ?
    AND employee_id = ? ');
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 1, 'S');
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 2, 'N');
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 3, 'ELABORADO');
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 4, 'PENDIENTE');
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 5, cur."x");
    DBMS_HS_PASSTHROUGH.BIND_VARIABLE@TEST (c, 6, cur."y");
    nr := DBMS_HS_PASSTHROUGH.EXECUTE_NON_QUERY@TEST (c);
    DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@TEST (c);
    COMMIT;
    END LOOP;
    END;
    You can help, how better the performance for update 500,000 record by record in MS SQL Server. I need advantages of use Oracle Transparent Gateway for Microsoft SQL Server.
    your's can suggest my another solution ?
    Thanks.

    Hi,
    There are no real parameters to tune the gateways. You should turn on gateway debug tracing and check the SQL that is being sent to SQL*Server to make sure is update statements and nothing else.
    If this is the case then the time taken will be down to various factors, such as network delays, processing on SQL*Server and so on.
    How long does it take to update the same number of records directly on SQL*Server without the Oracle or the gateway involved or if you use another non-Oracle client to do the same updates across a network, if a network is involved ?
    It may be possible to improve performance by changing the HS_RPC_FETCH_REBLOCKING parameter, so have a look at this note in My Oracle Support -
    Tuning Generic Connectivity And Gateways (Doc ID 230543.1)
    Regards,
    Mike

  • Undeployment poor performance

    Hi,
    JDevoloper has poor performance when deploying und undeploying a application. Below is a example: 3 minutes!
    Maybe it's caused by the BEA-000449 messages? How can I avoid this messages and how can I speed up deployment and esp
    Any suggestions?
    Stefan
    Details
    [Application termination requested.  Undeploying application myapp.]
    [09:45:29 AM] ----  Deployment started.  ----
    [09:45:29 AM] Target platform is  (Weblogic 10.3).
    <17.12.2009 09:46 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
    [09:47:23 AM] Undeploying Application...
    <17.12.2009 09:47 Uhr MEZ> <Warning> <Deployer> <BEA-149085> <No application version was specified for application 'myapp'. The undeploy operation will be performed against the currently active version 'V2.0'.>
    [09:47:24 AM] Application Undeployed Successfully.
    <17.12.2009 09:47 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
    <17.12.2009 09:48 Uhr MEZ> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
    [09:48:37 AM] Elapsed time for deployment:  3 minutes, 9 seconds
    [09:48:37 AM] ----  Deployment finished.  ----
    [Application myapp stopped and undeployed from Server Instance IntegratedWebLogicServer]

    Hi Uma,
    Did you finally resolve this issue?
    I am facing the same problem.
    Thanks,
    Vibhu

  • EA6500 Poor Performance

    Hello all,
    I recently upgraded from a Linksys Wireless-N router that was only a few years old to the EA6500. Since upgraded I have constantly been have performance and range issues with the new router. On many of my devices the WiFi drops constantly and the only way to stop it is to reset the router. With range I am only getting around 20 feet before I start having connection issues. With my old wireless-N router I was receiving around double that. I even have problems with devices such as my Google TV being able to located my PC for streaming content unless I manual connect using the IP address. Wired connections work without any issues.  
    I have changed the channels and the spectrum so nothing is changing automatically. At this point I am at a loss of what to do. Is it just that this router has poor performance? I would be surprised since this was fairly expensive. 
    Any help or tips would be appreciated.

    I dont know with your old N router, but the EA500 is a dual band. Try changing the wireless name of the 5ghz so that it is different from the 2.4 ghz. This prevents the dual band wireless computers or devices from switching between the 5 and 2.4 ghz causing wifi drops.
    Check if your router's firmware is up to date. You can click on connectivity and click on check for updates. If there's a new firmware available, better update it.
    Set your wireless security to WPA2 personal, on both the 2.4 and 5 ghz band.
    Bring the router as far away as possible from any wireless device that could cause interference, even electronic devices.
    Place your router in an open elevated place to eliminate wireless signal obstruction.
    If your have access points or extenders in the network, make sure that the devices are in sync with the settings of your new router.
    Make sure you are using the recommended power adapter of the new router and not the power adapter of your old N router (this happened to my friend before).

  • How to improve Query Performance

    Hi Friends...
    I Want to improve query performance.I need following things.
    1.What is the process to findout the performance?. Any transaction code's and how to use?.
    2.How can I know whether the query is running good or bad ,ie. in performance praspect.
    3.I want to see the values i.e. how much time it is taking to run?. and where the defect is?.
    4.How to improve the query performance?. After I did the needfull things to improve performance, I want to see the query execution time. i.e. it is running fast or not?.
    Eg..
    Eg 1.   Need to create aggregates.
    Solution:  where can I create aggregates?. Now I'm in production system. So where I need to create? .i.e. indevelopment or in Quality or in Production system?.
    Any chenges I need to do in Development?.Because I'm in Production system.
    So please tell me solution for my questions.
    Thanks
    Ganga
    Message was edited by: Ganga N

    hi ganga
    please refer oss note :557870 : Frequently asked questions on query performance
    also refer to
    Prakash's weblog
    /people/prakash.darji/blog/2006/01/27/query-creation-checklist
    /people/prakash.darji/blog/2006/01/26/query-optimization
    performance docs on query
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c8c4d794-0501-0010-a693-918a17e663cc
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/064fed90-0201-0010-13ae-b16fa4dab695
    This is the oss notes of FAQ on query performance
    1. What kind of tools are available to monitor the overall Query Performance?
    1.     BW Statistics
    2.     BW Workload Analysis in ST03N (Use Export Mode!)
    3.     Content of Table RSDDSTAT
    2. Do I have to do something to enable such tools?
    Yes, you need to turn on the BW Statistics:
      RSA1, choose Tools -> BW statistics for InfoCubes
      (Choose OLAP and WHM for your relevant Cubes)
    3. What kind of tools is available to analyze a specific query in    detail?
    1.     Transaction RSRT
    2.     Transaction RSRTRACE
    4.  Do I have an overall query performance problem?
    i. Use ST03N -> BW System load values to recognize the problem. Use the  number given in table 'Reporting - InfoCubes:Share of total time (s)'  to check if one of the columns %OLAP, %DB, %Frontend shows a high   number in all Info Cubes.
    ii. You need to run ST03N in expert mode to get these values
    5. What can I do if the database proportion is high for all queries?
    Check:
    1.     If the database statistic strategy is set up properly for your DB platform (above all for the BW specific tables)
    2.     If database parameter set up accords with SAP Notes and SAP Services   (EarlyWatch)
    3.     If Buffers, I/O, CPU, memory on the database server are exhausted?
    4.     If Cube compression is used regularly
    5.     If Database partitioning is used (not available on all DB platforms)
    6. What can I do if the OLAP proportion is high for all queries?
    Check:
    1.     If the CPUs on the application server are exhausted
    2.     If the SAP R/3 memory set up is done properly (use TX ST02 to find bottlenecks)
    3.     If the read mode of the queries is unfavourable (RSRREPDIR, RSDDSTAT,  Customizing default)
    7. What can I do if the client proportion is high for all queries?
    Check whether most of your clients are connected via a WAN  connection and the amount of data which is transferred   is rather high.
    8. Where can I get specific runtime information for one query?
    1.     Again you can use ST03N -> BW System Load
    2.     Depending on the time frame you select, you get historical data or current data.
    3.     To get to a specific query you need to drill down using the InfoCube  name
    4.      Use Aggregation Query to get more runtime information about a   single query. Use tab All data to get to the details.   (DB, OLAP, and Frontend time, plus Select/ Transferred records,  plus number of cells and formats)
    9. What kind of query performance problems can I recognize using ST03N
       values for a specific query?
    (Use Details to get the runtime segments)
    1.     High Database Runtime
    2.     High OLAP Runtime
    3.     High Frontend Runtime
    10. What can I do if a query has a high database runtime?
    1.     Check if an aggregate is suitable (use All data to get values "selected records to transferred records", a high number here would  be an indicator for query performance improvement using an aggregate)
    2.     o Check if database statistics are update to data for the   Cube/Aggregate, use TX RSRV output (use database check for statistics  and indexes)
    3.     Check if the read mode of the query is unfavourable - Recommended (H)
    11. What can I do if a query has a high OLAP runtime?
    1.     Check if a high number of Cells transferred to the OLAP (use  "All data" to get value "No. of Cells")
    2.     Use RSRT technical Information to check if any extra OLAP-processing is necessary (Stock Query, Exception Aggregation, Calc. before   Aggregation, Virtual Char. Key Figures, Attributes in Calculated   Key Figs, Time-dependent Currency Translation)  together with a high number of records transferred.
    3.     Check if a user exit Usage is involved in the OLAP runtime?
    4.     Check if large hierarchies are used and the entry hierarchy level is  as deep as possible. This limits the levels of the hierarchy that must be processed. Use SE16 on the inclusion tables and use the List of Value feature on the column successor and predecessor to see which entry level of the hierarchy is used.
    5.     Check if a proper index on the inclusion  table exist
    12. What can I do if a query has a high frontend runtime?
    1.     Check if a very high number of cells and formatting are transferred   to the Frontend (use "All data" to get value "No. of Cells") which   cause high network and frontend (processing) runtime.
    2.     Check if frontend PC are within the recommendation (RAM, CPU MHz)
    3.     Check if the bandwidth for WAN connection is sufficient
    REWARDING POINTS IS THE WAY OF SAYING THANKS IN SDN
    CHEERS
    RAVI

  • Project Server 2013 Poor Performance

    Hi Guys
    On a new build of Project Server, we are experiencing poor performance across the board, Site Collection, Central Admin, everything is slow.
    We have allocated 12GB and Quad core (lower end of the recommend scale). However as there are no users, I would expect it to be fine at the moment (Search is not setup or anything, just a simple service app with a pwa site provisioned).
    What things can we check? From looking on the internet, Distributed Cache crops up a lot. Can this bring performance right down?
    For the record, we have March 2013 PU and Oct 2013 CU applied.

    Hello,
    There could be a number of causes, it is very difficult to diagnose without understanding the farm infrastructure. Can you give details of:
    Number of servers in the farm + Specs
    If virtual, is the host server over committed? Have you set up reservations for memory and CPU?
    What is the storage?
    What is the network speed between servers / storage etc?
    Do you have any Anti-Virus software installed on the servers? If so, have you tested with it disabled on all servers in the farm?
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Poor performance when dragging item within a list loaded with images - Flex 4

    Hi,
    I have a custom built List component that is using a TileLayout. I am using a custom itemRenderer to load images into this list from our server (in this test, 44 images rae loaded). I have enabled dragEnabled and dragMove so that I can move items around within the list. The problem comes when I start dragging an item. The dragging operation is very slow and clunky.
    When I move the mouse to drag the item, the dropIndicator does not get refreshed for a few seconds and the movement feels like my PC is lagging pretty badly. I've also noticed that during this time my CPU usage is spiking up to around 25-40%. The funny part is I can scroll the list just fine without any lag at all, but the minute I drag the application starts to lag really bad. I do have some custom dragOver code that I used to override the dragOverHandler of the list control, but the problem persists even if I take that code out. I've tried with useVirtualLayout set to both true and false and neither setting made a difference. 
    Any ideas as to what could be causing the poor performance and/or how I can go abouts fixing it?
    Thanks a lot in advance!

    Ahh, good call about the Performance profiler. I'm pretty new to the profiling thing with Flex (haven't used Builder Pro before
    the Flex 4 beta) so please forgive me
    I found some interesting things running the performance profiler but I'm not sure I understand what to make of it all. I cleared the Performance Profile data when right before I loaded the images into the list. I then moved some images around and then captured the Profiling Data (If I understand Adobe correctly, this is the correct way to capture performance information for a set of actions).
    What I found is there is a [mouseEvent] item that took 3101ms with 1 "Calls" (!!!!). When I drill down into that item to see the Method Statistics, I actually see three different Callees and no callers. The sum of the time it took the Callees to execute does not even come close to adding up to the 3101 ms (about 40ms). I'm not sure what I can make of those numbers, or if they are even meaningful. Any insight into these?
    The only other items that stand out to me are [pre-render] which has 863ms (Cumulative Time) / 639ms (Self Time), [enterFrameEvent] which has 746ms / 6ms (?!), and [tincan] (what the heck is tincan?) which has times of 521ms for both Cumulative and Self.
    Can anyone offer some insight into these numbers and maybe make some more suggestions for me? I apologize for my ignorance on these numbers - as I said, I'm new to the whole Flex profiling thing.
    Many thanks in advance!
    Edit: I just did another check, this time profiling only from the start of my drag to the end of my drop, and I still see [mouseEvent] taking almost 1000ms of Cumulative Time. However, when I double click that item to see the Method Statistics, no Callers or Callees are listed. What's causing this [mouseEvent] and how come it's taking so long?

  • EOS WFT software causing wireless network failure.

    I have set up the Canon WFT pairing software and the EOS utilities on my windows 8 laptop computer.
    Normally when connecting my camera wirelessly to my computer I use a TP-Link portable hub to which nothing else is connected and there is no internet connected, this works fine as I can use it easily anywhere I go without having to set up the WFT settings on the camera again for different wireless hubs ip addresses etc.
    When I am not using the WFT software my computer will be connected to a different wireless hub for internet access and connection to other devices I live between two houses in different locations each has it's own virgin high speed wireless broadband  internet system.
    The WFT Pairing software starts automatically when I start my computer whether or not I intend to use it.
    Since installing the WFT pairing software I noticed my laptop had poor performance connecting to the internet via the wireless internet hubs with frequent disconnections and that other devices on the same wireless network also had problems and lost their connections. This also occurs when I visit friends when I use their networks.
    At first I did not connect this issue to the pairing software, however it became evident it was this laptop causing the problem because it occures in every location I connected to a wireless hub.
    I have now conclusively proved that after stopping the WFT pairing software in Windows Task Manager all devices connected to the wireless hub function normally again in all locations restart the pairing software and they will all fail again.
    Is this a known problem? and is there a solution for it?

    Hi RobertTheFat
    Yes thats clear, Since I found it was the cause of the problem I have it's automatic start up disabled and I check with task manager to make sure it is not running when not using the WFT, then when I need it I start it manually but it doesn't change the fact that it causes the network problem when it is needed and running.
    I have a suspicion that either Windows 8 or Norton 360 might be preventing it from detecting the camera and that it is constantly poling the network trying to find the camera, this could be the reason the network goes down.
    An interesting fact is that I do not have any problem accessing anything in the house such as the NAS drive or printer or other computers when it is running, but it pulls down the external connections so i cannot get reliable internet connections which makes it difficult to get any remote help.

  • CRIO Poor Performance - Where have my MIPS gone?

    I have a cRIO based system that is used to control a motor for a particular application. The application has been developed and enhanced over the years and is currently using about 50% of the CPU. The RT Controller is a cRIO-9012. I have recently been asked to add a 1 kHz (or more) loop function to the cRIO application. I can only achieve a maximum loop rate of about 200 Hz. When I told the customer this, he asked how fast my controller was, to which I replied 400 MHz. “Where is all the CPU power going?”, he asked. He's now thinking of replacing the cRIO Controller with an mbed with C code to get the performance he requires, which is a pity since I'd like to continue developing the application in LabVIEW.
    Following on from his question, “where is all the CPU power going?”, I decided to write a simple application to test the cRIO 9012's performance. Below is the code I used to perform the evaluation:
    With just the bottom loop running, which reports CPU load over the cRIO Controller's serial port, I have a CPU load of 7.0%. This is the baseline.
    I then add the "execution" loops as shown above the bottom loop, one at a time and recoded the CPU load. Here are the results:
    1 Loops - 18.3% load (11.3% extra)
    2 Loops - 29.4% load
    3 Loops - 45.5% load
    4 Loops - will not run!
    I have two problems/concerns.
    Concern 1
    The cRIO 9012 has a 400 MHz processor, which has 760 MIPS of processing power. The rate of the simple loop is 2 kHz and each loop takes about 11% of the CPU power. That is, each loop uses up 83.6 MIPS and each loop iteration uses up 41,800 instruction cycles. Where are the 41,800 instructions going? Even if there was a context switch after each loop iteration, this would account for 150 to 200 instruction cycles. Each loop is only doing an integer increment, timing check, compare and branch. These should only take up about 4 instruction cycles (8 if you want to be generous). If this was programmed in C, you could get bare metal performance that allows a single loop rate of something like 40 MHz or with an RTOS something like 2 MHz. Instead, my maximum loop rate is something like 20 kHz.
    Where are the "wasted" 41,600 instructions per loop iteration going? This is only 0.5% efficient!
    Concern 2
    Why does adding the 4th "execution" loop cause the application to halt (or at least not send data over the serial port)?
    I like programming on the desktop using LabVIEW and I like programming the FPGA using LabVIEW. The RT Controller is however becoming an embarrassment. Is it really the case that the best additional loop rate I can add to an existing application that already uses 50% of the cRIO Controller's CPU can only be 200 Hz maximum?

    Thanks for all the feedback.
    MajorTom,
    Changing to timed loops instead of while loops makes the performance worse. For 2 Loops, rather than a CPU load figure of 29.4% (22.4% after removing base load) it shoots up to 78.4% (71.4% after removing base load). That is, it runs about 3 times slower, which takes the "efficiency" down from 0.5% to 0.15% efficient.
    TimothyA,
    I tried making the "execution" loops subVIs (with Preferred Execution System = other 1, with the top level = other 2) and that solved the four "execution" loops problem. Thanks, one of my concerns is now resolved (I'll mark it as such once the conversation quietens down).
    The execution time is still large with the 2 loops taking 29.1% of the CPU, which is the same as before.
    I tried using the "reduced" us wait next multiple CLN.vi, but it appears to be in LabVIEW 2014 and I'm using LabVIEW 2013. Any chance of resaving it as LabVIEW 2013?
    crossrulz,
    Thank you for pointing me to the table in the CompactRIO Developer's Guide. I assume you’re talking about Figure 3.5. Priorities and Execution Systems available in LabVIEW Real-Time. I didn't realise that Execution Systems are limited in the number threads (would be nice to get a warning when this happens). This will make interesting reading and experimentation.
    All,
    I’ve tried various loop limiting rates including Timed Loops and While Loops with RT Wait Until Next Multiple, RT Wait, Wait Until Next Multiple and Wait and the best perform is from the two RT waits. The worst performance was from the Timed Loops.
    In summary, I’ve solved the problem regarding how to run more parallel loops, but I still get very poor performance with each loop interaction taking about 41,800 instructions when it “should” take more about 200 instruction cycles. All I want is to be able to run a loop at at least 1 kHz on my cRIO-9012 when I already have an application that takes up about 50% of the CPU. I have the threat of the code being moved to an mbed using C, which I’m trying to resist. Surely a 400 MHz controller can have a 1 kHz loop and not take up more than 10% of the CPU.

Maybe you are looking for