I've noticed lately that Mingle2 has been progressively taking longer to load each page.

At first, I thought it was network. Nope, it's only Mingle. Every other site loads much faster.

Then I thought it was my browser extensions. Nope, I switched off the ones I haven't been using and that appeared to be the culprits. Still no difference.

That leaves me with 2 ideas:

1) There is a network bottleneck somewhere between here and the Mingle servers. (I could investigate this, and either prove or disprove this theory pretty easily.)

2) The bot activity on Mingle has created so many accounts and messages that it's beginning to slow down the servers. If left unchecked, this could cause the servers to crash, similar to a DDoS attack.


Therefore, I am curious how many other users have noticed the slowdown in loading times for Mingle2 pages. Anyone?

If it's not just me, then perhaps I should run some tests and do some digging to collect some data. I used to do this as a beta-tester to help a company improve service and performance. I might be able to uncover some usual information to pass onto the Mingle2 Tech Support. It's time-consuming though. That's why I need to know first if other users have been experiencing the same problem.

Sometimes the site is slow but most of the time it is ok.

Yes i have noticed some major slowdowns lately as well.

wait you mean its not suppose to be ?

ot only abit today but i did get one down for maintenance

I decided to track latencies for each component that the page needs to load. The initial document whose name is a number listed in the URL that appears in the address bar appears to be the primary culprit.

What this means in layman's terms...

The Mingle servers are slow.

In more technical terms, the server is taking 2 - 4 seconds to compose and send the first byte of this document. The document itself is small, about 8 to 10 kilobytes.

With a 20 Mbps connection, it should take maybe 60 milliseconds to receive this document. Transmission does not appear to be the problem though.

The problem seems to be the time the server takes to process the query, which - from what I have been told by people more knowledgeable than I - means the problem likely lies in an SQL for the database.

To place it back into layman's perspective...

Most servers can process the request in 200 - 500 milliseconds, but the Mingle2 servers are taking 2000 - 4000 milliseconds. That's 8x - 10x slower than most internet servers.

This is just from a simple cursory check, and that's just the single largest slowdown.

In this same cursory check, I've notice a number of other high latencies in the range of 120 ms - 600 ms. These are items which normally should take about one-quarter the time to process and receive. But combined, they are adding yet another 3.5 seconds to the page's load time, making the total load times 5 - 8 seconds for any given page on Mingle2.

That's pretty darn slow.

In each case, it's the TTFB number that's unusually high. TTFB means Time To First Byte. This is the time it takes for 1) your computer to send the request, 2) the server to receive the request, process it, and compose the response, and 3) for your computer to receive the response from the server.

I can look at other numbers which tell me the actual transmission times for the initial request and the response. Those numbers are low, less than 15 ms combined.

This means that the server is taking a long time to process the request. There are zero problems with the actual transmission between your computer and the server.

So again, it's not the internet. The Mingle2 servers are just slow.

Very slow at times often too many people accessing site.

I get that message sometimes.

Yes I have noticed it is taking 500 ms longer to load a page, which if my calculations are correct and I open 120 pages a day I lose 1 minute.But I just wasted 2 minutes writing this note.Where can I apply for a refund ? A bit like when I ask what time is it in NY, it finds me 4,700 million results and it only took 0.9 seconds.By the time I have read the results I'll have to check what year it is.