|
|
Tally_NSA Loyal user Essex, UK 222 Posts |
I've been getting several "cannot connect to database" errors on this site, with only 50 odd people online. This is an indication that the MySQL server is struggling to handle a database which is too big. Some kind of culling needs to be put in place to prevent it become pandemic.
As someone with a BSc in Computer Science, and 15 years experience of being a Web Master for some very large sites (Infinity Ward offical forums, Treyarch official forums, and Activision's main website) I can tell you that: 1. You have way too many forums. You should ideally slim them down to the bare essentials; 2. You need some sort of control over necroing. When someone bumps an old thread, this puts a strain on the MySQL server fetching the old data, while sharing its resources for newer threads and posts. Putting in a rule that necroing an old thread with little new to contribute, when a new thread instead of a necro, would help. When someone does this, just cut their new post out of the old thread and create a new topic for it will really take the strain off the MySQL server; 3. You need to archive threads which are more than 5 years old. This is a lot of work, but pays off the dividends if carried out. These are just suggestions. Take them or leave them. But, if you do nothing, the problem will only get worse as time goes on. |
Salguod Nairb Room 101 0 Posts |
I haven't had any issues in over a month, but I'm connecting from Kuwait.
We shall meet in the place where there is no darkness...
|
Tally_NSA Loyal user Essex, UK 222 Posts |
Quote:
On Jun 27, 2016, Salguod Nairb wrote: I don't see your name amongst the list of staff members (even when you reverse your name back the way it should read). So, you will excuse me if I ignore your post, since I am addressing the senior staff here. However, having said that, I will say that location simply has nothing to do with it. I have reproduced this error using various VPNs from different locations in the world. All the same. Remember the words of Spock: "I have never been to Romulus. But still I know it exists". In other words, just because the problem does not affect you, it does not mean it does not exist. |
Artie Fufkin Special user 853 Posts |
Reading Tally's 226 posts, he's apparently an expert on everything! ... even when he's not.
I spend way too much time on the Café, and never have any sort of connection issue at all. |
Tally_NSA Loyal user Essex, UK 222 Posts |
Quote:
On Jun 27, 2016, Artie Fufkin wrote: Quote:
Remember the words of Spock: "I have never been to Romulus. But still I know it exists". In other words, just because the problem does not affect you, it does not mean it does not exist. FYI - a user cannot create a database error. That's the fault of the site itself. So, I also don't have any "connection issues at all". It's this site having problems with users. |
Dave Scribner Assistant Manager Lake Hopatcong, NJ 4849 Posts |
Quote:
Reading Tally's 226 posts, he's apparently an expert on everything! ... even when he's not. Well said Artie.
Where the magic begins
|
Gene Café Forum Developer Howard City, MI 276 Posts |
1. You have way too many forums. You should ideally slim them down to the bare essentials;
2. You need some sort of control over necroing. When someone bumps an old thread, this puts a strain on the MySQL server fetching the old data, while sharing its resources for newer threads and posts. Putting in a rule that necroing an old thread with little new to contribute, when a new thread instead of a necro, would help. When someone does this, just cut their new post out of the old thread and create a new topic for it will really take the strain off the MySQL server; 3. You need to archive threads which are more than 5 years old. This is a lot of work, but pays off the dividends if carried out. 1: Ideally, yes, but it's how Steve wants it. 2&3: Tried that and it was overwhelmingly and negatively received by the membership. There's a history here that cannot be ignored, but we do from time to time try to determine if there are things we can do without ... well ... "blanking" off the members. There are basically two reasons that error appears (other than the times backups are run): The site's search engine (both search and indexing processes) and the database's InnoDB storage engine. Since we were forced to use the InnoDB storage engine (it's a long story) I have been working on optimizing the queries and indexes to work efficiently with it. There are several processes which use total DB row counts, which of course is something InnoDB doesn't store like MyISAM does. I've been working on migrating things (the problematic stuff, anyway) to different processes but that's taking a while because I don't want to shut everything down except for small periods of time here and there. Wholesale changes are sure to be coming sometime in the future but until I can take the necessary time to get everything worked out it's just going to have to wait. I'd love nothing more than to splice up the data into more manageable chunks, but believe me, the outcry from members - if it's like anything in the past - would be a never ending discussion and we certainly don't want to go through all of that again. There's a LOT more to the story, but it is what it is and we're dealing with it the best we can. Now, if we could get google-type search speed and results on a frosted flakes budget ... ... on second thought, nevermind the frosted part.
Somebody kick me off the computer, will ya?
|
The Magic Cafe Forum Index » » The Magic Café Tech Help Area » » Database Is Now in Serious Trouble » » TOPIC IS LOCKED (2 Likes) |
[ Top of Page ] |
All content & postings Copyright © 2001-2024 Steve Brooks. All Rights Reserved. This page was created in 0.02 seconds requiring 5 database queries. |
The views and comments expressed on The Magic Café are not necessarily those of The Magic Café, Steve Brooks, or Steve Brooks Magic. > Privacy Statement < |