- Messages
- 26,281
- Reaction score
- 5,875
- # of dives
- I'm a Fish!
DataBaseWhat's DB?
Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.
Benefits of registering include
DataBaseWhat's DB?
As diversteve said, it's short for data base. While we have several servers working in unison to handle the web end, we only have one mondo server handling the data base. The data base is the record of all of ScubaBoard and how you are able to navigate to an individual thread, post or PM. Think of it like a book with a very detailed table of contents. At any moment we have between 2,000 and 3,000 people all trying to access that book, looking up the table of contents and then zipping to the part they want to read. Back in January, it was over 150 queries per second and I am sure it's grown since then. When there is an error or disconnect, it's never obvious to the query. It just keeps looking, tying up the db for everyone one else who wants to look at it. Almost every DB has errors, but when a part of your system dies, in this case the part intended to speed things up (mem-cache), the problem snowballs and the usability of the system degrades. Add to that a rather aggressive traveling schedule over the past few months for the technical staff, and this one kind of got away from us. Mea culpa. You can bet that we will be tuning mem-cache as we see fit over the next few days and we are looking forward to getting the new design and move away from this buggy one which doesn't quite fit any more. I hope this helps.What's DB?
As diversteve said, it's short for data base. While we have several servers working in unison to handle the web end, we only have one mondo server handling the data base. The data base is the record of all of ScubaBoard and how you are able to navigate to an individual thread, post or PM. Think of it like a book with a very detailed table of contents. At any moment we have between 2,000 and 3,000 people all trying to access that book, looking up the table of contents and then zipping to the part they want to read. Back in January, it was over 150 queries per second and I am sure it's grown since then. When there is an error or disconnect, it's never obvious to the query. It just keeps looking, tying up the db for everyone one else who wants to look at it. Almost every DB has errors, but when a part of your system dies, in this case the part intended to speed things up (mem-cache), the problem snowballs and the usability of the system degrades. Add to that a rather aggressive traveling schedule over the past few months for the technical staff, and this one kind of got away from us. Mea culpa. You can bet that we will be tuning mem-cache as we see fit over the next few days and we are looking forward to getting the new design and move away from this buggy one which doesn't quite fit any more. I hope this helps.
Just an aside... Facebook runs exclusively on MySQL. We aren't anywhere near to Facebook in terms of users or throughput. They do pretty well for using a play toy DB.Of course, I assume you are using MySQL? Cool DB. They think they are a real DB, and in fact are, up to a point. Perhaps you have reached it?
User Friendly Interface
The user interface is designed specifically for efficiency, making it quick and easy for your users to intuitively browse and post on your forums.
Of course, I assume you are using MySQL? Cool DB. They think they are a real DB, and in fact are, up to a point. Perhaps you have reached it?
Cause I see the major delays on query based "clicks".
Don't get me wrong. I am a big fan of PG, but it might not scale either. So you are left with Oracle, IBMDB2, or "horrors" MS_SQL (which is a damn fine platform).
As diversteve said, it's short for data base. While we have several servers working in unison to handle the web end, we only have one mondo server handling the data base. The data base is the record of all of ScubaBoard and how you are able to navigate to an individual thread, post or PM. Think of it like a book with a very detailed table of contents. At any moment we have between 2,000 and 3,000 people all trying to access that book, looking up the table of contents and then zipping to the part they want to read. Back in January, it was over 150 queries per second and I am sure it's grown since then. When there is an error or disconnect, it's never obvious to the query. It just keeps looking, tying up the db for everyone one else who wants to look at it. Almost every DB has errors, but when a part of your system dies, in this case the part intended to speed things up (mem-cache), the problem snowballs and the usability of the system degrades. Add to that a rather aggressive traveling schedule over the past few months for the technical staff, and this one kind of got away from us. Mea culpa. You can bet that we will be tuning mem-cache as we see fit over the next few days and we are looking forward to getting the new design and move away from this buggy one which doesn't quite fit any more. I hope this helps.