Announcement

Collapse
No announcement yet.

vBulletin Survey

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by Scott MacVicar View Post
    Won't be APC, just an OP Code cache of some sort be it XCache, APC, eaccelerator or Zend Platform.

    I think what Kier is trying to say is that we'll use much more aggressive caching with the vBulletin 4.
    That's excellent news and is sure to make many of the big boards happy campers.
    Toddler from Hell

    Comment


    • #62
      Which is better eaccelerator or APC linked to in the recommended software page?

      Comment


      • #63
        Originally posted by Scott MacVicar View Post
        Actually I remember this now.

        There was a few performance issues with PHP 5.2.0 and 5.2.1, mostly down to the new memory manager that needed a few tweaks.

        Regardless of what was said in the past the latest PHP 5.2 is what we're recommending for customers.
        Thanks Scott

        Originally posted by Kier View Post
        I have also included APC in our recommendations - we will be making far more use of opcode caches in vBulletin 4.

        With vB3 there is a huge benefit from using an opcode cache, but we don't take specific advantage of their features.

        This wil be reversed in vBulletin 4, where we will code with those running an opcode cache as our target platform. Those not running an opcode cache will still be able to run vBulletin 4, but they will be at a distinct disadvantage.
        Sounds great!

        There are over one billion users on the web, and that is predicated to double much faster than it took to get the 1stB - sites are getting more and more traffic, and catering for 'busy' sites is definitely a step in the right direction.

        Look forward to seeing the vB dev blog (or similar) - being able to speak with devs about stuff like this goes towards keeping us customers happy
        What's Special About Ruby on Rails?

        Comment


        • #64
          I'd recommend APC over eAccelerator, as it seems to have a far more active development team.

          Comment


          • #65
            Originally posted by Kier View Post
            I'd recommend APC over eAccelerator, as it seems to have a far more active development team.
            Ok, thanks .

            Comment


            • #66
              Well I upgraded last night and I am getting the same problems again (the ones that we downgraded to php4 to avoid).

              They are always: 'MySQL Error : MySQL server has gone away' and almost always (least this time they were all) to do with 'UPDATE session'. The boards are running 3.6.8 with latest patch. However the boards themselves seem to be running ok (in fact a lot faster if anything).

              Are there any specific modules vB needs on the server? (Such as curl, mycrypt etc).
              What's Special About Ruby on Rails?

              Comment


              • #67
                Did you upgrade both MySQL and PHP? How did you upgrade, using a binary or a self-compile? What platform are we talking about, and what versions? APC or no?

                Comment


                • #68
                  Originally posted by Razasharp View Post
                  They are always: 'MySQL Error : MySQL server has gone away' and almost always (least this time they were all) to do with 'UPDATE session'. The boards are running 3.6.8 with latest patch. However the boards themselves seem to be running ok (in fact a lot faster if anything).
                  What is your wait_timeout set to in the MySQL Configuration files? You can see this in the admin CP under Maintenance -> Diagnostics -> System Information. Select to view MySQL Variables. It is the last one.

                  Had frequent server has gone away errors on a site that I manage after the host upgraded to PHP 5.2.5 and MySQL 5.0.51 a few days ago. They had set the wait timeout to 15 seconds. The default from MYSQL is 28800 seconds. After having them increase the value to 120 seconds, the errors have ceased. The hosting account is a cPanel account so not sure if they upgraded with the cPanel package or by compiling themselves. Could be an issue in the newer version of MySQL packages distributed by cPanel.
                  Translations provided by Google.

                  Wayne Luke
                  The Rabid Badger - a vBulletin Cloud demonstration site.
                  vBulletin 5 API

                  Comment


                  • #69
                    Thanks for your help both!

                    Originally posted by Kier View Post
                    Did you upgrade both MySQL and PHP? How did you upgrade, using a binary or a self-compile? What platform are we talking about, and what versions? APC or no?
                    I used Cpanels easyapache (via WHM) to upgrade. We're running CENTOS Enterprise 3.9 i686 and have APC installed (do I need to update APC after moving up to php 5?)

                    Web Server Apache v1.3.41
                    PHP 5.2.5
                    PHP Max Post Size 55.00 MB
                    PHP Maximum Upload Size 2.00 MB
                    PHP Memory Limit 8.00 MB
                    MySQL Version 5.0.45-community
                    MySQL Packet Size 64.00 MB

                    Data Usage 546.38 MB
                    Index Usage 341.97 MB
                    Attachment Usage 69.16 MB
                    Avatar Usage 2.40 MB
                    Profile Picture Usage 2.45 MB

                    I noticed it only upgraded to MySQL Version 5.0.45, and not 5.0.51 (there was only an option to check mysql 5 in the settings).


                    Originally posted by Wayne Luke View Post
                    What is your wait_timeout set to in the MySQL Configuration files? You can see this in the admin CP under Maintenance -> Diagnostics -> System Information. Select to view MySQL Variables. It is the last one.

                    Had frequent server has gone away errors on a site that I manage after the host upgraded to PHP 5.2.5 and MySQL 5.0.51 a few days ago. They had set the wait timeout to 15 seconds. The default from MYSQL is 28800 seconds. After having them increase the value to 120 seconds, the errors have ceased. The hosting account is a cPanel account so not sure if they upgraded with the cPanel package or by compiling themselves. Could be an issue in the newer version of MySQL packages distributed by cPanel.
                    Wait timeout is set to 30, although if you see the original thread here, we tried upping the timeout, and it while it helped with the errors, it also made the boards run 'slow':

                    I was still getting the errors even at 90s, so I recomplied Apache, and upgraded php to 5.2 and forced reinstalled mysql to the latest version (and did the same for ACP). Basically got everything on the server to the latest versions... however the problem didnt go away, about once a day I would get sent the error - 10 min or so difference in the start time of the first email to the time in the last email.

                    So I upped the wait timeout as you suggested... no good, so upped it again, in the end I put it to about 5000 (!) and the errors stopped... however I noticed recently that the site was running slow/sluggish - where it was not as responsive after clicking on a link. So I changed the wait time out back to 30, which resolved the speed issue, but guess what? The error messages have started again! :-(
                    Apart from downgrading back to php4 (which helped cut down the errors considerably) we upgraded the ram by an extra gig (to 2GB) which then stopped them. I also off-loaded attachments to a different server (by using a different script - but only supporting members could upload them anyway).

                    I will try increasing the wait time to 90, and see how that goes.

                    Thanks again for your help both.
                    What's Special About Ruby on Rails?

                    Comment


                    • #70
                      The first thing I'd do is up your PHP memory limit to 16MB, but that's almost certainly not going to address your MySQL problem. Diagnosing MySQL server problems isn't really my forte, but hopefully someone will have some ideas.

                      Just had a thought - are you using the 'mysql' dbtype in config.php, or 'mysqli'? It's possible that could make a difference.

                      Comment


                      • #71
                        Thanks Kier, will change memory limit to 16MB.

                        Config.php has mysql selected, shall I change it to mysqli? (do I just need to edit the config file? Or run an upgrade script of some sort too?)

                        Edit: Just tried changing it and got this:

                        Fatal error: Call to undefined function mysqli_init() in /home/my-site/public_html/includes/class_core.php on line 1030
                        Last edited by Razasharp; Sat 19 Apr '08, 11:33am.
                        What's Special About Ruby on Rails?

                        Comment


                        • #72
                          Interesting that your PHP build doesn't include mysqli... maybe it's a special parameter you need to pass to easyapache. I'm afraid it's a long time since I ran easyapache so I'm a bit rusty.

                          Comment


                          • #73
                            I think there was a checkbox for it... I must have missed it

                            I'll re-run it tonight, although the errors seemed to have stopped after increasing the wait timeout to 120 (but then the weekends are not our busiest times)

                            If there are any more probs I'll report back.. thanks for your help.

                            I think I may have to get a new server anyway, as I guess the new SN/album features in 3.7 will pretty much need it

                            Update: All done - now running with mysqli. Will report back if there are any more error messages.
                            Last edited by Razasharp; Sat 19 Apr '08, 5:04pm.
                            What's Special About Ruby on Rails?

                            Comment


                            • #74
                              Update: Had 4 error emails today... will try increasing wait timeout to 120 and see how that goes.
                              What's Special About Ruby on Rails?

                              Comment


                              • #75
                                Originally posted by Razasharp View Post
                                Update: All done - now running with mysqli. Will report back if there are any more error messages.
                                I have about the same; Could you please post the steps?

                                Comment

                                widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                                Working...
                                X