7 Replies Latest reply: Jul 3, 2014 12:32 AM by Bhabani Ranjan RSS

    ODI Studio is too Slow

    2665441

      Hi All,

       

      We are doing ODI developemnet.

       

      We use ODI studio to load the work Repository and do the work.

       

      But its two slow to perform any activity from that.

       

      the Connection will take 20-30 min

      the if we click on any Project it will take 5 min to expand

      and similary like any click will take more than 2-3 min to get it done.

       

      Please help me to get ride of this problem.

       

      If any once can suggest any thing for performance improvement

      We are not able to do any development because of this.

        • 1. Re: ODI Studio is too Slow
          KKT

          Hi,

           

          Are you trying to login in ODI studio as normal user , if it is please login using Supevisor user and check the performance.

           

          Also there is a bug defined by Oracle for the same issue.

           

          Thanks,

          ~KKT~

          • 2. Re: ODI Studio is too Slow
            990603

            Hi,

             

            This sort of problem occurs when the database where the repository sits is physically located at a distance from where you are logging from, or there is network latency issue to the ODI repository DB.  If this is the case, can you get a virtual machine or remote desktop to a machine the is close to the ODI database repository.

             

            The reason for this is is the repository is a relational database, and every time you are performing an action in ODI studio, it's executed on the relational DB.

             

            Thanks

            Arv

            • 3. Re: ODI Studio is too Slow
              JeromeFr

              In the same kind of idea, connecting to the repository through VPN might be really slow.

               

              Arv's suggestion of having a VM or RDC closer to the repository is a good idea.

              • 4. Re: ODI Studio is too Slow
                mRainey

                This does sound like a network issue as stated previously. But, just in case you need an extra bump in processing power behind ODI Studio, you can modify the max memory used by the JVM. On ODI 11g, go to <ODI_HOME>/oracledi/client/odi/bin and edit the odi.conf file. Modify the line AddVMOption -XX:MaxPermSize=256M, changing the value to something greater, within your systems memory limitations.

                 

                Hope this helps.

                 

                Regards,

                Michael Rainey

                • 5. Re: ODI Studio is too Slow
                  2665441

                  Hi KKT,

                   

                  We are logging through Supevisor user only.

                   

                   

                  Hi JeromeFr

                   

                  Is there any way by which we can increase the performance with out the RDC and VM?

                  • 6. Re: ODI Studio is too Slow
                    JeromeFr

                    Being physically on a computer closer (network-wise) to the repository ?

                    If the problem comes from the network, you need to reduce the distance (or improve your network...).

                     

                    I would start with mRainey's suggestion though, to be sure it's not just a memory problem.

                     

                     

                    Regards,

                    JeromeFr

                    • 7. Re: ODI Studio is too Slow
                      Bhabani Ranjan

                      Want to add one more suggestion to the above.

                       

                      If you are working on dev and you are vpn connected, then develop the project in local and import it in your remote studio. This will minimize network latency as you will not be browsing the repository again and again.

                       

                      Things to be taken care of: Internal ID in case of ODI 11g.

                      1. The ODI Admin team might hesitate to keep adding new IDs to the repository.

                      2. All team members should have a different Repository ID to avoid collision.

                      3. You have to sacrifice the configured agent

                       

                      Bhabani