vB5 Memory Errors

[ShannonA]

I'm testing out a vB5 on a large web site (~650k threads, 20M posts). I'm seeing some real lag opening forums some of the time, which I'm starting to guess is a memory issue, because our largest forum fails entirely:

[Wed Oct 24 12:37:38.279596 2018] [:error] [pid 19794] [client 75.101.48.41:59825] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 28672 bytes) in /var/www/vb/core/vb/database/mysqli.php on line 230

Suggestions?

[Wayne Luke]

More information is needed.

https://www.vbulletin.com/forum/forum/vbulletin-5-connect/vbulletin-5-connect-questions-problems-troubleshooting/vbulletin-5-support-issues-questions/4005558-required-information-to-obtain-support

[ShannonA]

1. vBulletin Version

5.4.4

1. PHP Version

7.0.30-0+deb9u1

1. MySQL Version

mysql Ver 15.1 Distrib 10.1.26-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

1. Any Addons installed

Third-Party Login Google and Twitter are the only Products running

1. Does the issue occur in a default style?

Yes

1. Does the issue occur using the English language provided?

Yes.

1. Error message on the screen

Screen goes white. Error message "[Wed Oct 24 12:37:38.279596 2018] [:error] [pid 19794] [client 75.101.48.41:59825] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 28672 bytes) in /var/www/vb/core/vb/database/mysqli.php on line 230" shows up in log files

1. Browser and Browser version used.

Google Chrome Version 69.0.3497.100 (Official Build) (64-b

1. Did you clear the browser cache and did the error continue?

Yes.

1. A list of steps that can be used to recreate the issue.

Click on forum with slightly more than 5M posts.

1. If the issue is an Invalid Server response, the web server and PHP logs that correspond wit

[Wed Oct 24 12:37:38.279596 2018] [:error] [pid 19794] [client 75.101.48.41:59825] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 28672 bytes) in /var/www/vb/core/vb/database/mysqli.php on line 230

[Wayne Luke]

Can you obtain a stack trace of the error?

To do this, put the site in Debug Mode and recreate the error. The debug error and stack trace should be shown on the screen.

[ShannonA]

It shows a blank screen because of the memory exhaustion, so it never gets to the point where it can shows a debug error or stack trace.

The information in the log file looks the same:

Wed Oct 24 15:14:04.694842 2018] [:error] [pid 19794] [client 75.101.48.41:54362] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vb/core/vb/search/core.php on line 517,

[Wed Oct 24 15:14:04.698364 2018] [:error] [pid 19794] [client 75.101.48.41:54362] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 684032 bytes) in /var/www/vb/core/vb/database/mysqli.php on line 230,

[ShannonA]

PS: The URL you gave for vb5 debug mode doesn't work.

I got the info from https://www.vbulletin.com/forum/blog...vb5-debug-mode

[Wayne Luke]

Please increase the allocated memory to 384 MB within your php.ini file.

[ShannonA]

That makes it work, but opening forums is still abysmally slow. (That one takes 7-12 seconds, on a robust machine that's what we usually use for the database backend of our forums setup.)

[Wayne Luke]

5 Million posts in a single forum is going to take a longer time to load as it is.

What version of Memcached do you have installed?

What version of Sphinx Search do you have installed?

[Wayne Luke]

In debug mode, what is the MySQL time? Should show at the bottom of the page.

[ShannonA]

5 Million posts in a single forum is going to take a longer time to load as it is.

So, 7-12 seconds forum loading time is standard for a large forum on vB5? That's a show-stopper if true. I get less than a second on both vB4 and my test XenForo setup.

What version of Memcached do you have installed?

What version of Sphinx Search do you have installed?

This is a minimal test setup, so there's nothing extraneous install. I did add memcached 3.0.1 to see if it made any difference. (It didn't.)

In debug mode, what is the MySQL time? Should show at the bottom of the page.

I don't see a MySQL time. Here's what the Debug info shows: Debug Information

• Page ID: 75
• Parent ID: 53
• Page Template ID: 2
• Route ID: 92
• Page Type: custom
• Screen Layout ID: 1
• Screen Layout Template: screenlayout_display_full
• Channel ID: 27
• Node ID: 27
• Database Asserts: 222 (?)
• AJAX Requests: 2
• Facebook Active: Yes
• Style ID: 34
• Templates/Renders: 36/105
• CSS Templates: 4
• JS Files: 9
• Included Files: 161
• Autoloaded Classes: 156
• Current Time: Fri, 26 Oct 2018 14:20:06 -0700
• Page Time: 8.3614

[Wayne Luke]

You have to configure memcached in the /core/includes/config.php file. vBulletin won't start using it magically.

Sorry, click on the question mark next to Database Asserts.

[ShannonA]

You have to configure memcached in the /core/includes/config.php file. vBulletin won't start using it magically.

Sorry, click on the question mark next to Database Asserts.

It looks like this is the problematic MySQL:

Time Taken: 6.9546070098877 Memory Used: 13553664
SELECT DISTINCT node.starter AS nodeid FROM node as node LEFT JOIN node AS starter ON starter.nodeid = IF(node.starter = 0, node.nodeid, node.starter) WHERE starter.sticky <> '1' AND node.contenttypeid <> 37 AND node.parentid = 27 AND node.showpublished > 0 AND node.showapproved > 0 AND node.viewperms = 2 AND node.inlist = 1 AND node.contenttypeid <> 22 AND node.protected <> '1' ORDER BY starter.lastcontent DESC,node.nodeid ASC /**getSearchResults**/

[ShannonA]

No further thoughts on the show-stopping access time we're seeing from that lookup?

[ShannonA]

Alrighty. Looks like we're probably going with XenForo. Thanks.