Disappointed, uninstalled.

Thanks! I use ionCube so I installed APC. I'll see how that works.

My php is a little out of date, however. I'll prob wait to upgrade to vB 3.5 before I go to high with the php version though.

Originally Posted by tavenger5

I'll prob wait to upgrade to vBulletin 3.5 before I go to high with the php version though.

Upgrading vB will help the most as vBSEO uses the hook system to pre-cache data and minimize queries

Originally Posted by tavenger5

Thanks! I use ionCube so I installed APC. I'll see how that works.

My php is a little out of date, however. I'll prob wait to upgrade to vB 3.5 before I go to high with the php version though.

I agree with Juan on upgrading to 3.5. So much more optimized.

Originally Posted by treasureman

Yes the issue has been resolved. I can not tell you exactly what the problem was but can tell you everything I did, so I guess it had to be one of these things, or perhaps a combination.

I requested a "server optimization" from Vbulletin.com and they gave he some things to do, which were:

Upgraded PHP from 4.4.1 to 4.4.2
Made changes to my.cnf
Made changes to httpd.conf
Disabled persistent connections

The entire thread, outlining specific changes is here:
Optimization Request - vBulletin Community Forum

I did all the recommendations except for uninstalling Zend, which is required by VBSeo

Now, it seems that the loads were still a little high for the first couple of days, but have settled down now. Loads are still higher than without VBSeo, but it is manageable.

Hope this helps!

Uninstall Zend and use Ioncube with APC. You will see a decrease in load times

I backup ionCube also, I use it with eAccelerator and everything is smooth like silk.

is f

Originally Posted by TECK

I backup ionCube also, I use it with eAccelerator and everything is smooth like silk.

I use eAccelerator, too (0.9.4). KICKS the butt of Zend (version 2.x, anyway), and is even faster APC (because APC only caches code, whereas EA optimizes + caches).

Also plays nice with ionCube when ion is used in the html directory.

Drops some people's server load in half.

I definitely give eAccelerator my thumbs up at the moment.

Teck, do you have IonCube and eAccelerator somehow both installed in php.ini itself? I'd LOVE to do that, if you don't mind sharing how it's done. Would make upgrading far easier.

Ya, they are both in php.ini file. EA 0.9.5 beta2 with PHP 5.1.2 versions.
I don't like to have the loader in the html folder, all server files are outside the root.

Code:

;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
;

; IonCube Loader
zend_extension = "ioncube_loader_lin_5.1.so"

; eAccelerator
; You must uncomment one (and only one) line from the following to load
; eAccelerator extension.
;extension = "eaccelerator.so"
zend_extension = "eaccelerator.so"

; The amount of shared memory (in megabytes) that eAccelerator will use.
; "0" means OS default. Default value is "0".
eaccelerator.shm_size = 16

; The directory that is used for disk cache. eAccelerator stores precompiled
; code, session data, content and user entries  here. The same data can be
; stored in shared memory also (for more quick access).
eaccelerator.cache_dir = "/home/username/tmp/eac"

; Enables or disables eAccelerator. Should be "1" for enabling or
; "0" for disabling. Default value is "1".
eaccelerator.enable = 1

; Enables or disables internal peephole optimizer which may speed up code
; execution. Should be "1" for enabling or "0" for disabling.
; Default value is "1".
eaccelerator.optimizer = 1

; Enables or disables debug logging. Setting this to 1 will print information
; to the log file about the cach hits of a file.
eaccelerator.debug = 0

; Set the log file for eaccelerator. When this option isn't set then the data
; will be logged to stderr
eaccelerator.log_file = "/home/username/var/log/eac"

; A string that's prepended to all keys. This allows two applications that use the
; same key names to run on the same host by setting this in .htaccess or in the main
; configuration file for the whole webserver.
eaccelerator.name_space = ""

; Enables or disables PHP file modification checking. Should be "1"
; for enabling or "0" for disabling. You should set it to "1" if you want
; to recompile PHP files after modification. Default value is "1".
eaccelerator.check_mtime = 1

; Determine which PHP files must be cached. You may specify the number of
; patterns (for example "*.php *.phtml") which specifies to cache or
; not to cache. If pattern starts with the character "!", it means to ignore
; files which are matched by the following pattern. Default value is "" that
; means - all PHP scripts will be cached.
eaccelerator.filter = ""

; Disables putting large values into shared memory by "eaccelerator_put()"
; function.
; It indicates the largest allowed size in bytes (10240, 10K, 1M). The "0"
; disables the limit. Default value is "0".
eaccelerator.shm_max = 0

; When eAccelerator fails to get shared memory for new script it removes 
; all scripts which were not accessed at last "shm_ttl" seconds from shared
; memory. Default value is "0" that means - don't remove any files from
; shared memory.
eaccelerator.shm_ttl = 0

; When eAccelerator fails to get shared memory for new script it tryes to 
; remove old script if the previous try was made more then "shm_prune_period"
; seconds ago. Default value is "0" that means - don't try to remove any
; files from shared memory.
eaccelerator.shm_prune_period = 0

; Enables or disables caching of compiled scripts on disk. It has no effect
; on session data and content caching.
; Default value is "0" that means - use disk and shared memory for caching.
eaccelerator.shm_only = 0

; Enables or disables cached content compression. Default value is "1" that
; means enable compression.
eaccelerator.compress = 1

; Compression level used for content caching. Default value is "9" which it
; is the maximum compression level.
eaccelerator.compress_level = 9

; Determine where keys, session data and content will be cached. The possible
; values are:
; "shm_and_disk" - cache data in shared memory and on disk (default value)
; "shm"          - cache data in shared memory or on disk if shared memory
;                  is full or data size greater then "eaccelerator.shm_max"
; "shm_only"     - cache data in shared memory
; "disk_only"    - cache data on disk
; "none"         - don't cache data
eaccelerator.keys     = "shm_and_disk"
eaccelerator.sessions = "shm_and_disk"
eaccelerator.content  = "shm_and_disk"

; The script paths that are allowed to get admin information and do admin
; controls
eaccelerator.allowed_admin_path = ""

I'm with Dreamhost, shared account. I made my own PHP compiling script, the one posted on their support wikipedia was buggy... Not to mention a security risk since you use php engine files in the root. That's really bad. You should have there only html stuff, no server files.

My html and forum stuff is in /home/username/site.com

Also, I clean my EA /tmp folder with a CronJob, every morning at 4am. Basically, any tmp file older then 7 days gets deleted... good to keep the webthings tight...