Slow site

Question

Slow site

Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

Ed Wagner (8/26/2015)
Jeff Moden (8/26/2015)
Heh... good grief. Between 20 and 60 seconds between every click now (10:30PM EDST). This is brutal. I sure hope you good folks can get to the bottom of this soon. Signing off for the night.
I was seeing the same thing at the same time. I was up to > 90 seconds to reply and gave up. Now (10:56 EDT) it's still around 60 seconds to bring up the page to submit a post.

still around 30-60 seconds per click currently.

Guess I will try back tomorrow.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Eirikur Eiriksson SSC Guru Points: 182915 More actions · Answer 2

The site is once again very slow, up to 90sec between clicks :sick: and images particularly slow!

😎

~~Quick~~ test

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 3

Morning all,

It's been a rough night for the site - things came good for an hour or so, but the problem is very much still ongoing. More chasing this morning... will update when we have more news.

Thanks,

Rob

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 4

Right, we're good again as of 0830 UTC. Continuing to monitor, of course...

Thanks,

Rob

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 5

Fingers crossed, it's a permanent fix this time too:

Engineers isolated the issue to an aggregation router that was experiencing connectivity issues. The aggregation router was recabled, resolving the networking issues on 27 August, at 08:36 UTC

So Jeff, I think your guess of a dodgy cable was correct all along ;-).

Thanks everyone for your patience, and sorry again for the annoyance.

Cheers,

Rob

Ed Wagner SSC Guru Points: 287026 More actions · Answer 6

robert.chipperfield (8/27/2015)
Fingers crossed, it's a permanent fix this time too:
Engineers isolated the issue to an aggregation router that was experiencing connectivity issues. The aggregation router was recabled, resolving the networking issues on 27 August, at 08:36 UTC
So Jeff, I think your guess of a dodgy cable was correct all along ;-).
Thanks everyone for your patience, and sorry again for the annoyance.
Cheers,
Rob

Thanks for staying with it and keeping on them. Unless they know about it, they'll never know they need to do anything.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 7

robert.chipperfield (8/27/2015)
Fingers crossed, it's a permanent fix this time too:
Engineers isolated the issue to an aggregation router that was experiencing connectivity issues. The aggregation router was recabled, resolving the networking issues on 27 August, at 08:36 UTC
So Jeff, I think your guess of a dodgy cable was correct all along ;-).
Thanks everyone for your patience, and sorry again for the annoyance.
Cheers,
Rob

Heh... you can tell that my suggestion was from experience. In the last 3+ decades, I've seen this happen more than once. What some folks forget is that, at the frequencies being passed over the cables, even a little-too-tight of a bend in the cable can cause the cable to "go bad". In the early days, even laying cables to close together would sometimes cause cross-talk in the cables. Heh... and you should see what happens when you don't have a good ground on your shielded cable. Now, that's fun!

I'm sure that the others will agree with me a profound and very hearty "THANK YOU" for your diligence in isolating this problem. As a regular denizen of this fine forum, reasonable response times is critical to experience. Thank you again.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 8

Heh... and you should see what happens when you don't have a good ground on your shielded cable. Now, that's fun!

Yep - I do some ham radio in my spare time, and even microfractures in the foil screen of coax cable caused by repeated coiling and uncoiling leads to horrendous loss in the GHz bands. When you get up to those frequencies, everything starts looking like an attenuator... but I digress!

Cheers for now,

Rob

SQLRNNR SSC Guru Points: 281334 More actions · Answer 9

Thanks for staying on top of it and restoring service.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Ed Wagner SSC Guru Points: 287026 More actions · Answer 10

Let me echo Jeff and Jason - thank you for your persistence!

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 11

@robert.chipperfield,

Praise and kudos to you and the team, again. The site has been absolutely awesome and better than it has been for longer than we thought. That hardware/cable problem must have been going slowly bad over quite a time.

Thank you folks again!

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 12

Robert Chipperfield (Redgate)

Ten Centuries

Points: 1380

September 4, 2015 at 5:42 am

#1824596

Thanks, Jeff!

Sean Lange SSC Guru Points: 286590 More actions · Answer 13

Maybe there are rats chewing on the wires. The performance has been steadily getting worse over the last few days. As of today the site is basically unusable for me. It is nearly 30 seconds for every page load. Hopefully it gets resolved.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

mister.magoo SSC-Forever Points: 47174 More actions · Answer 14

Sean Lange (9/10/2015)
Maybe there are rats chewing on the wires. The performance has been steadily getting worse over the last few days. As of today the site is basically unusable for me. It is nearly 30 seconds for every page load. Hopefully it gets resolved.

Agreed, but intermittently, almost like the rats keep getting distracted.

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

Robert Chipperfield (Redgate) Ten Centuries Points: 1380 More actions · Answer 15

Sorry to hear that - we've not seen a repeat of the same packet loss we were seeing since it was fixed, so it feels like it must be unrelated.

If you can either drop a reply on this thread, or email me (I'm sure you can guess my @red-gate.com address from my SSC username!) while it's in go-slow mode for you, I'll do my best to jump on while it's happening, and see if I can dig into the cause.

Thanks,

Rob