Jump to content

Slow page loads, hardly any users

Recommended Posts

Guys, since upgrading from 2.3.6 we've basically lost so much traffic I'm convinced the slow page loads have to be causing an issue for members and visitors.

Our VPS spec is as follows:
8 Cores at 2.26+ GHz (shared)
2Gb guaranteed RAM
120Gb RAID10 Disk Space

The server can be fine one minute, then the next we're waiting 10-15 seconds for a page to load, and even then it loads as though we're on dial-up. This can be with as few as 10 users on the site. I've noticed it doesn't really matter how many users are on, the problem is just seriously random (see screenshot).

post-116929-087564300 1282203124_thumb.p

I've been working with the host who explained they were having kernel issues and they've just recently applied the most recent patches, etc, but it always seems my page load issues appear when the server load starts creeping up, so would appear it's a resource issue on our site and not particularly the server. I could be way off and wrong, I just don't know.

Our my.cnf file is pretty much standard though I've tried tweaking it before which didn't help, so more or less resorted back to the default my.cnf. I've also tried finding out if there are any tweaks possible for litespeed but couldn't determine this either.

If anyone is able to make any suggestions or provide some form of assistance with an example my.cnf file for a 2Gb RAM setup I'd be really grateful. We're running IPBoard along with IPDownloads.

Thanks in advance

Link to comment
Share on other sites

A few of us had similar issues and some of it is caused by search engines indexing your site at a furious rate after upgrading to version 3. You should add say a 5 second delay to your robots.txt file plus edit your Google Webmaster account and set up a similar delay. This should make a big difference.

Hope this helps.


Link to comment
Share on other sites

Thanks for the response 3DKiwi, I already have a delay in the robots of 10 seconds, just edited the webmaster tools for google though, hopefully this may make a difference from google. I'm still open for suggestions regarding my.cnf if anyone can suggest anything :)

# Example MySQL config file for large systems.


# This is for a large system with memory = 512M where the system runs mainly

# MySQL.


# You can copy this file to

# /etc/my.cnf to set global options,

# mysql-data-dir/my.cnf to set server-specific options (in this

# installation this directory is /var/lib/mysql) or

# ~/.my.cnf to set user-specific options.


# In this file, you can use all long options that a program supports.

# If you want to know which options a program supports, run the program

# with the "--help" option.

# The following options will be passed to all MySQL clients


#password	= your_password

port		= 3306

socket		= /var/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server


port		= 3306

socket		= /var/lib/mysql/mysql.sock


key_buffer = 256M

max_allowed_packet = 1M

table_cache = 256

sort_buffer_size = 1M

read_buffer_size = 1M

read_rnd_buffer_size = 4M

myisam_sort_buffer_size = 64M

thread_cache_size = 8

query_cache_size= 16M

# Try number of CPU's*2 for thread_concurrency

thread_concurrency = 8

# Don't listen on a TCP/IP port at all. This can be a security enhancement,

# if all processes that need to connect to mysqld run on the same host.

# All interaction with mysqld must be made via Unix sockets or named pipes.

# Note that using this option without enabling named pipes on Windows

# (via the "enable-named-pipe" option) will render mysqld useless!



# Disable Federated by default


# Replication Master Server (default)

# binary logging is required for replication


# required unique id between 1 and 2^32 - 1

# defaults to 1 if master-host is not set

# but will not function as a master if omitted

server-id	= 1

# Replication Slave (comment out master section to use this)


# To configure this host as a replication slave, you can choose between

# two methods :


# 1) Use the CHANGE MASTER TO command (fully described in our manual) -

#    the syntax is:



#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;


#    where you replace <host>, <user>, <password> by quoted strings and

#    <port> by the master's port number (3306 by default).


#    Example:



#    MASTER_USER='joe', MASTER_PASSWORD='secret';


# OR


# 2) Set the variables below. However, in case you choose this method, then

#    start replication for the first time (even unsuccessfully, for example

#    if you mistyped the password in master-password and the slave fails to

#    connect), the slave will create a master.info file, and any later

#    change in this file to the variables' values below will be ignored and

#    overridden by the content of the master.info file, unless you shutdown

#    the slave server, delete master.info and restart the slaver server.

#    For that reason, you may want to leave the lines below untouched

#    (commented) and instead use CHANGE MASTER TO (see above)


# required unique id between 2 and 2^32 - 1

# (and different from the master)

# defaults to 2 if master-host is set

# but will not function as a slave if omitted

#server-id       = 2


# The replication master for this slave - required

#master-host     =   <hostname>


# The username the slave will use for authentication when connecting

# to the master - required

#master-user     =   <username>


# The password the slave will authenticate with when connecting to

# the master - required

#master-password =   <password>


# The port the master is listening on.

# optional - defaults to 3306

#master-port     =  <port>


# binary logging - not required for slaves, but recommended


# Point the following paths to different dedicated disks

#tmpdir		= /tmp/		

#log-update 	= /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables

#bdb_cache_size = 64M

#bdb_max_lock = 100000

# Uncomment the following if you are using InnoDB tables

#innodb_data_home_dir = /var/lib/mysql/

#innodb_data_file_path = ibdata1:10M:autoextend

#innodb_log_group_home_dir = /var/lib/mysql/

#innodb_log_arch_dir = /var/lib/mysql/

# You can set .._buffer_pool_size up to 50 - 80 %

# of RAM but beware of setting memory usage too high

#innodb_buffer_pool_size = 256M

#innodb_additional_mem_pool_size = 20M

# Set .._log_file_size to 25 % of buffer pool size

#innodb_log_file_size = 64M

#innodb_log_buffer_size = 8M

#innodb_flush_log_at_trx_commit = 1

#innodb_lock_wait_timeout = 50



max_allowed_packet = 16M



# Remove the next comment character if you are not familiar with SQL



key_buffer = 128M

sort_buffer_size = 128M

read_buffer = 2M

write_buffer = 2M


key_buffer = 128M

sort_buffer_size = 128M

read_buffer = 2M

write_buffer = 2M



Link to comment
Share on other sites

How do you enable the performance feature in the footer?

ACP > System > Tools / Settings > 'system' > General Configuration >

Scroll down to 'Other General Settings'

Set 'Debug level' to '1: Show server load, page generation times and query count'

Do not set to (2) or (3) for normal use (unless testing) as it potentially exposes sensitive information.
Link to comment
Share on other sites

Usually that's down to how your server is configured, so not something you can easily adjust (unless you have a VPS / Dedicated server) :) , Although I am not sure what to actually adjust though (this section of the forum is out of my area really of being able to help, well usually anyway), I replied as I noticed your question was a straightforward one on where to switch them on.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...