vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   mysql_connect Database Errors (https://vborg.vbsupport.ru/showthread.php?t=243703)

Videx 06-08-2010 04:19 PM

No way. Going through this recently on the HG forums, I know on a good day 100 users could easily share 25 mysql connections. Conversely, if something isn't working right, a single user could fill all 25. Really, on oversold shared servers the problem is usually cpu load anyway ("4.0 per cpu is acceptable" AAAGH).

I use that chatbox (as a shoutbox) and don't get the bots. Odd that some people do.

Chalex4 06-08-2010 04:20 PM

I see, so I could potentially have hundreds of people on the site, but if more than 26 people tried to load a page at exactly the same time, one would receive an error. This could be a problem if I ever want to properly expand.

What would you recommend usually for a larger board?

EDIT: That's interesting Videx, I guess it all depends on how often your site is being indexed already.

Zachery 06-08-2010 04:33 PM

Quote:

Originally Posted by Videx (Post 2050579)
No way. Going through this recently on the HG forums, I know on a good day 100 users could easily share 25 mysql connections. Conversely, if something isn't working right, a single user could fill all 25. Really, on oversold shared servers the problem is usually cpu load anyway ("4.0 per cpu is acceptable" AAAGH).

I use that chatbox (as a shoutbox) and don't get the bots. Odd that some people do.

No way what? It is possible for 25 users alone to kill those 25 connections, just not likely.

It really depends on how much and what if anything they're doing.

Chalex4 06-15-2010 10:18 AM

I seem to be getting some of these errors now as well (not as many though):

PHP Code:

Database error in vBulletin 4.0.3:

Invalid SQL:

                
SELECT *
                
FROM vb_style
                WHERE 
(styleid 11 AND userselect 1)
                    OR 
styleid 11
                ORDER BY styleid ASC
                LIMIT 1
;

MySQL Error   MySQL server has gone away
Error Number  
2006
Request Date  
TuesdayJune 15th 2010 02:10:56 AM
Error Date    
TuesdayJune 15th 2010 02:12:35 AM
Script        
http://www.atkcommunity.com/threads/2508-EA-Week-on-Steam
Referrer      
IP Address    xx.xxx.xx.xxx
Username      
Unregistered
Classname     
vB_Database
MySQL Version 



ChopSuey 06-15-2010 01:33 PM

That is your MySQL server going down.

Boofo 06-15-2010 01:53 PM

Quote:

Originally Posted by Zachery (Post 2050576)
It comes down to mean you can have 25 active mysql connections total. If you had 26+ users online at the same time, or possibly higehr, your users will get those errors.

That number is kind of mis-leading though, as most connections will run in a faction of a second and close. If you have some poorly structured queries, that can cause problems with connections not closing fast enough. But, 25 is kind of low, I agree. Hostgator is set up that way unless you go the VPS setup or higher.

Zachery 06-16-2010 12:52 AM

Quote:

Originally Posted by Boofo (Post 2054052)
That number is kind of mis-leading though, as most connections will run in a faction of a second and close. If you have some poorly structured queries, that can cause problems with connections not closing fast enough. But, 25 is kind of low, I agree. Hostgator is set up that way unless you go the VPS setup or higher.

It really depends on a large number of things, if those 25 users are poking, clicking around, possibly using one of those fancy ajax chat boxes, 25 connections can get gobbled up a whole ton faster. Downloading large attachments from the database can also cause issues.

ChopSuey 06-16-2010 06:26 AM

I'd really get a better host. 25 is a bad limit lol.

Videx 06-16-2010 09:47 AM

Quote:

Originally Posted by ChopSuey (Post 2054371)
I'd really get a better host. 25 is a bad limit lol.

It seems to be going around nowadays though. The ads trumpet unlimited storage and bandwidth, which is true. But not too many new website owners have any idea what a MySQL connection is, nor any idea the software they'll use may need it. But from personal experience even worse is the "acceptable" CPU load on those oversold shared servers. You'll start getting mysql errors long before you get anywhere near the 25 connection limit.

ChopSuey 06-16-2010 09:57 AM

One of the reasons i chose a VPS hahah. Shared hosting sucks.


All times are GMT. The time now is 12:28 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.02186 seconds
  • Memory Usage 1,747KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_php_printable
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (2)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete