Is the forum running slow again for anyone else??

[ubeaut]

Thanks guys

Please keep us informed.

Because it's up and down it's not easy to find the problem. And no it's not the search bots. The forums have been under attack with many thousands of hits from suspect IP over the last month or so, all of which have been being blocked instantly over the last week after a clean-up of the 4 biggest ones which accounted for over 1/2 million hits in 20 days. Some of these were attached to long time members IP addresses.

We need as much feedback as possible to help us keep on top of the problem.

• when it slows down, eg: Times between 7:30am - 8:05am or 3:20pm to 3:40pm etc
• length of time and what you were doing, eg: editing a post, loading the forum, reporting a post, submitting reply, etc
• Any message you might get, eg: Timed out. or other.

Any and all info will be greatly appreciated.

Cheers - Neil

[ubeaut]

Reply to this thread above.
2:51pm 1 July 20
37 sec to show reply.


​EDIT:
This reply 2.5 sec

[poundy]

I'll add some data - but it will just show the absence of trends when looking at my workflow.

I have a browser tab open to the forum. Randomly along the day I might get a moment to look - I'll use the " new posts" link from the menu to get a list of updated threads. The query takes usually 3-5 seconds to return; I'll time a few so the next time I see an outlier to that I have some metrics, but that usually is pretty constant. Assuming I get time to go further, I'll click each link, usually bottom up, to go to the next unread post - when doing that is when I often see the most noticeable pause, when it's trying to load the actual thread. Sometimes it's loaded in the usual 5-6 secs, but others it's 20+.

[poundy]

this morning things were working fine - and then one time at around 8:57am (SYD) a thread opened quite slowly, in the order of 15-20 secs. After reading another thread or two (normal speed) going back into the thread that was slow was fine, so it's not something in the thread its the server response that went slow.

[old1955]

Tried to open about half hour or so ago. Finished up going to Metalwork Forums and then used it’s link to open WWF which seemed much quicker. No times as have only just found the above request.

[woodPixel]

WWF is hosted on Midphase. Go into the control panel and enable Cloudflare.

It will automatically add on all the features the site seeks... Cloudflare Hosting | Improve Security & Speed | Midphase

Zero risk.

[elanjacobs]

8:05pm Melbourne time

46 seconds to load this thread, 8 seconds to get the reply box, 59 seconds to post this reply (including the "are you sure you want to leave this page" message from Chrome at 26 seconds)

[poundy]

new report from me. 8:36pm the thread https://www.woodworkforums.com/f163/...38#post2195728 from my unread list started taking a long time to open. When that happened I opened a new tab and tried to open this thread, which also took a long time. 8:37 ticked over on my PC. All up probably 40 secs to load these two pages, so it was very localised to the server at that point.

[Treecycle]

I clicked on the go to last post button on this thread at 4:30pm and it took 30 secs. Most other posts open fairly quickly.
Just clicked go to first new post on this one 10 minutes later and it took 1 minute to open.

[Fekit]

TBH, this whole slow thing is getting a bit old. I just got;

Request Timeout

This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase 'Connection Timeout'.

In attempting to get to this point, I have clicked on every single bookmarked page that I have, 25+, none of them missed a beat. I still had to wait for this site.

[ubeaut]

More work done this evening from 7:30pm - 7:48pm.

Lets know if it's any better.

Not lightening fast but not far off. Way, way better than it had been, at least it is for me and I've done a ship load of speed tests over the last week.

[Fekit]

In a relative comparison to recent speeds, todays speed is lightening fast.

[steven]

Hi there

That timeout would have been caused by me backing up the database and then making a bunch of major changes to how it's configured. There would have been several periods where it was timing out for 10-20 minutes at a time. There is still some more to do over the next few days, but i'm hopeful we won't be seeing the table locking issues that have plauged the site quite badly for the last couple of weeks.

We're monitoring things today with some more minor tweaks likely to follow tonight.

thanks

[Treecycle]

Certainly be running well over the last day or so.

[rwbuild]

Yes, a lot more stable