I was wondering if anyone has run into the following symptomology:I'm using the SQL 2014 distributed replay to test a production workload on new hardware and SQL 2008 R2 SP3. I've set everything up and I decided for my first run I would use the synchronization mode as I figured it should take the same amount of time as the workload I captured (30 minutes.) I kicked off dreplay and it distributed events to the four nodes that I have configured and I'm seeing a reasonable pass rate of >95%. However its not playing it back at the rate I was expecting. Instead it's taking well over 300 minutes!I'm using a configuration file from MSDN, and I'm wondering if there is some option that should be tweaked, but I'm at a loss as to which one.Update: So I started poking around in the client log file and saw that I've got lots of error messages like this:2016-03-10 19:18:51:429 CRITICAL [Client Replay] Active connections exceed 8192, connection 125758 is waiting.Which probably points at what's going wrong, but I'm not sure what to do. Connection pooling?[code="xml"]<?xml version='1.0'?><Options> <ReplayOptions> <Server>server_name\replay_target_instance</Server> <SequencingMode>synchronization</SequencingMode> <ConnectTimeScale></ConnectTimeScale> <ThinkTimeScale></ThinkTimeScale> <HealthmonInterval>60</HealthmonInterval> <QueryTimeout>3600</QueryTimeout> <ThreadsPerClient></ThreadsPerClient> </ReplayOptions> <OutputOptions> <ResultTrace> <RecordRowCount>Yes</RecordRowCount> <RecordResultSet>No</RecordResultSet> </ResultTrace> </OutputOptions></Options>[/code]
↧