Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Enterprise Gateway Data Refresh Performance with SSD

Hi,

 

I wanna ask some question regarding Enterprise Gateway data refresh performance. 

 

Does it help if I install the Enterprise Gateway at an SSD drive instead of spinning drive? Just wondering...

 

Hope some expert could shed some light.

 

Thanks.

Need Help
  • JosefPrakljacic's avatar
    JosefPrakljacic
    6 years ago

    Hi Anonymous ,

     

    in short it does help.

     

    Longer version of my answer :-)

     

    1. The cloud service creates a query and the encrypted credentials for the on-premises data source. The query and credentials are sent to the gateway queue for processing.
    2. The gateway cloud service analyzes the query and pushes the request to Azure Service Bus.
    3. Azure Service Bus sends the pending requests to the gateway.
    4. The gateway gets the query, decrypts the credentials, and connects to one or more data sources with those credentials.
    5. The gateway sends the query to the data source to be run.
    6. The results are sent from the data source back to the gateway and then to the cloud service. The service then uses the results.

    In step 6, queries like Power BI refreshes and Azure Analysis Services refreshes can return large amounts of data. For such queries, data is temporarily stored on the gateway machine. This data storage continues until all data is received from the data source. The data is then sent back to the cloud service. This process is called spooling. We recommend you use a solid-state drive (SSD) as the spooling storage.

     

    Source

     

    If this post was helpful may I ask you to mark it as solution and give it some kudos?

    Have a nice day!

    BR,
    Josef

6 Replies

  • JosefPrakljacic's avatar
    JosefPrakljacic
    Solution Sage
    6 years ago

    Hi Anonymous ,

     

    in short it does help.

     

    Longer version of my answer :-)

     

    1. The cloud service creates a query and the encrypted credentials for the on-premises data source. The query and credentials are sent to the gateway queue for processing.
    2. The gateway cloud service analyzes the query and pushes the request to Azure Service Bus.
    3. Azure Service Bus sends the pending requests to the gateway.
    4. The gateway gets the query, decrypts the credentials, and connects to one or more data sources with those credentials.
    5. The gateway sends the query to the data source to be run.
    6. The results are sent from the data source back to the gateway and then to the cloud service. The service then uses the results.

    In step 6, queries like Power BI refreshes and Azure Analysis Services refreshes can return large amounts of data. For such queries, data is temporarily stored on the gateway machine. This data storage continues until all data is received from the data source. The data is then sent back to the cloud service. This process is called spooling. We recommend you use a solid-state drive (SSD) as the spooling storage.

     

    Source

     

    If this post was helpful may I ask you to mark it as solution and give it some kudos?

    Have a nice day!

    BR,
    Josef

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      JosefPrakljacic 

       

      Thank you so much for this!

       

      Just one more thing. My main system disk is spinning drive which is where my current Enterprise Gateway installed. Recently Infra has added 2 new SSD drive to my server. So if i just uninstall my current Enterprise Gateway and reinstall at this new SSD drive, I would see performance improvement right?

       

      Again thanks for replying.

      • JosefPrakljacic's avatar
        JosefPrakljacic
        Solution Sage
        6 years ago

        Hey Anonymous,

         

        I would say yes. But I'm not quite sure since I can't find any resource confirming this info.

         

        BR,

        Josef