MSDN Forum:SQL server performace issue with different storage

Mohan Agarwal 21 Reputation points
2020-09-21T07:45:05.797+00:00

Hi Team,

We are running same queries on two different SQL servers with version SQL server 2014 whereas we used different storage HP3PAR and NETAPP for both the servers but while execution of the queries for NETAPP storage we are getting wait type WRITELOG and ASYNC_NETWORK_IO.But we did not get any wait type during running the queries for HP3PAR storage.

Please let me know if this issue related with the storage of SQL server.

Thanks
Mohan

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,294 questions
Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
643 questions
0 comments
Accepted answer
  1. tibor_karaszi@hotmail.com 4,306 Reputation points
    2020-09-21T07:59:28.16+00:00

    You always have waits, the question is what wait types dominates your waits.

    I assume that you have read up on those two wait types and understand what they mean, so I won't go into that here.

    One possible reason is that you don't have the same execution plans for some queries, meaning that the load isn't the same.

    Another is of course that the disk subsystem don't have the same performance characteristics. For instance WRITELOG suggests that this is slower for writes compared to the the disk subsystem where you don't see these.

    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mohan Agarwal 21 Reputation points
    2020-09-21T13:48:40.91+00:00

    Thanks for reply.

    Our plan is to migrate the SQL server HP3PAR to NETApp but while performance testing we are facing wait type(WRITELOG and ASYNC_NETWORK_IO) on NETApp even no load is exist compare to prod server whereas no wait type showing during the performance baseline.

    Pls suggest the possible reasons of this issue.

    Thanks
    Mohan

    0 comments
  2. tibor_karaszi@hotmail.com 4,306 Reputation points
    2020-09-21T14:09:05.837+00:00

    Did you perform raw benchmarking tests between the storage solutions in the first place? That would be a prerequisite, or perhaps your NetApp solution might just be that much slower than the HP3PAR solution.

    But again, you always have waits! So it is likely that whatever you use to measure this perf baseline is hiding stuff (wait types) for you on your prod server, so what you see isn't the whole picture.

    Also ASYNC_NETWORK_IO has nothing to do with storage, it is the application that is slow to consume the data sent from SQL Server to the client.

    My guess is that your performance testing is simplified and misleading. Sine we have no insight in how this is done, we can't say more than that.

    Your best bet might be to bring in an external resource to help you with your baselining and measurements.

    0 comments
  3. Chang, Joe 111 Reputation points
    2020-09-21T23:36:53.223+00:00

    what is the connection between server and storage ? FC or iSCSI,
    if iSCSI, I suggest you shoot yourself now to avoid the problems later

    0 comments
  4. Mohan Agarwal 21 Reputation points
    2020-09-24T13:19:05.367+00:00

    We have the FC connection between server and storage.

    0 comments