mysql zu langsam mit phpbb

magejo

Registered User
Hallo!
Meine phpBB Datenbank ist 75 MB gross, laeuft auf einen Suse 10.1 Rootserver (bei s4y), flott und problemlos.
Neuerdings ist das Posten von Beitraegen langsam geworden, ich weiss nicht genau, woran es liegt.

die my.cnf Datei sieht so aus: - Weiss wer ne Abhilfe???

Gruss
Markus

my.cnf hier:
Code:
# The following options will be passed to all MySQL clients
[client]
#password    = your_password
port         = 3306
socket       = /var/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
set-variable=local-infile=0
port         = 3306
socket       = /var/lib/mysql/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 80
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Aenderungen
skip-bdb
query_cache_size = 10M
sort_buffer_size = 1M
read_rnd_buffer_size = 512K
join_buffer_size= 256K
tmp_table_size = 32M
max_heap_table_size=18M
thread_cache_size = 4
key_buffer_size=32M





# 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!
# 
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
# log-bin=mysql-bin

# 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:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    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:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    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
#log-bin=mysql-bin

# 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 = 4M
#bdb_max_lock = 10000

# 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 = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

# The safe_mysqld script
[safe_mysqld]
err-log=/var/lib/mysql/mysqld.log

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout
MOD: Bitte [noparse]
Code:
...
[/noparse]-Tags um Ausgaben, Code, etc. verwenden (im Editor auch mit '#' erreichbar). Danke!
 
Last edited by a moderator:
Bist du dir denn sicher, dass es an der Datenbank liegt?
Vielleicht ist auch dein Apache überlastet? Vielleicht irgendwelche Fehler im Script?
 
Bist du dir denn sicher, dass es an der Datenbank liegt?
Vielleicht ist auch dein Apache überlastet? Vielleicht irgendwelche Fehler im Script?

Apache laeuft ansonsten problemlos und sehr schnell. Das Problem tritt lediglich beim Speichern auf.
 
Sehr verwunderlich, denn auch beim Abrufen der Thread etc. werden ja MySQL Abfrage durchgeführt.

Was sagt denn das tuning Script zu deinem MySQL Prozess?
 
Schon mal probiert:

Code:
mysqladmin -u user -ppassword processlist

= in etwa:

Code:
+----+---------+-----------+------------+---------+-------+-------+------------------+
| Id | User    | Host      | db         | Command | Time  | State | Info             |
+----+---------+-----------+------------+---------+-------+-------+------------------+
| 23 | xxxxxxx | localhost | apachexxxx | Sleep   | 28332 |       |                  |
| 24 | xxxxxxx | localhost | apachexxxx | Sleep   | 27470 |       |                  |
| 88 | xxxxxx  | localhost |            | Query   | 0     |       | show processlist |
+----+---------+-----------+------------+---------+-------+-------+------------------+

x = unkenntlich

Ich empfehle mittels "top" die Prozesse "apache" "mysqld" und evtl "php"
genau zu beobachten. Treten hier "zombie"-Prozesse auf?

Das Problem hatten wir auch einmal. Es stellte sich heraus, daß der Code innerhalb von phpBB2 dafür verantwortlich war. Ich kann ich auch erinnern, daß fehlerhafte Daten innerhalb der Relationen die gleichen Symptome verursachen. Mich persönlich interessiert
aber mehr die Ausgabe von "top".
 
Last edited by a moderator:
Hatte das gleiche Problem, Grund dafür ist nicht MySQL sondern das Prüfen der IP-Adresse des Benutzers gegen schwarze DNS-Listen (Spamschutz).
Das lässt sich im Administrations-Bereich unter Server-Konfiguration > Sicherheit deaktivieren, danach geht das Posten eines Beitrags wesentlich schneller ;)
 
Back
Top