3 Replies Latest reply on Apr 12, 2018 7:30 AM by irina niyazov

    Hyper vs. TDE, how much faster?

    Mark Wu

      For those who are upgraded to 10.5, how much Hyper is faster than TDE in your env?

       

      Here is what I found based on more than one thousand extract test between Hyper and 10.4 TDE on Windows platform:

      • Hyper avg extract execution is 50% faster than TDE
      • Hyper avg extract size is 20% larger than TDE
      • Hyper view avg render time is 20% faster than TDE view render time


      What are your findings? Please share.

        • 1. Re: Hyper vs. TDE, how much faster?
          Ritesh Bisht
          • Hyper avg extract execution is 30% faster than TDE
          • Hyper avg extract size is 10% larger than TDE
          • Hyper view avg render time is 15% faster than TDE view render time
          • 2. Re: Hyper vs. TDE, how much faster?
            Mark Wu

            Interesting.... Ritesh's is consistently 'smaller' than mine for all the areas. Here is my findings again.... Definitely I do not see 3X improvements. Love to see more observations from others....

            • Hyper avg extract execution is 50% faster than TDE
            • Hyper avg extract size is 20% larger than TDE
            • Hyper view avg render time is 20% faster than TDE view render time
            • 3. Re: Hyper vs. TDE, how much faster?
              irina niyazov

              I am running 10.5.2 and 10.5.3  instances

               

              • Hyper avg execution is not faster it is actually slower by about 20%
              • Hyper avg extract size is 20%larger on extracts w.o comments, with comments it close to 40% larger. 
              • Hyper on EC2 m5.4xlarge- extracts get corrupted with each tabcmd refresh or publish as well as with each scheduled refresh .  Case opened with tech support,  no response
              • Hyper on EC2 r4.4xlarge - extracts get corrupted via tabcmd refresh or publish if record count in extract is greater than 20 million  Case opened with tech support,  no response