V-Server von Strato + Vbulletin = chaos?

B

BlackBaron106

New Member
Strato Server in den knien

Hallo,

Bin sehr froh auf dieses Forum gestoßen zu sein, vor allem weil hier auch das Vbulletin eingesetzt wird.

Denn genau darin habe ich derzeit Probleme:

Nachdem ich mit den Leistungen meines letzten hosters (webspaceverkauf.de) nicht zufrieden war, hatte ich mich entschlossen auf einen V-server umzusteigen um mehr performance zu erlangen.

Jetzt läuft alles auf dem neuen Server, 1 Vbulletin im Aufbau und eins das jetzt von einem wbb importiert wurde und zuvor 3 jahre online war.

Serverdaten:

CPU GenuineIntel, Intel(R) Celeron(R) CPU 2.40GHz

OS Linux 2.6.9-023stab044.16-enterprise

CPU NutzungLetzte 1 Minute 0.60
Letzte 5 Minuten 0.49
Letzte 15 Minuten 0.35

Gesamt Benutzt Frei
1.48 GB 1.45 GB 30.29 MB



Also der CPU scheint ja nicht wirklich belastet zu sein, aber wenn man eine Seite aufruft, lädt man des öfteren 30 sekunden lang bis eine seite überhaupt angezeigt wird... bilder, zb die Gallerie im portal laden teilweise erst nach einer minute.

Small Devils

Online sind rund 20 bis 30 user (mit gästen!)

Wieso habe ich dann ewig lange wartezeiten?
 
Last edited by a moderator:
Da gibt es nur eins zu sagen "Celeron". Ist für SQL-lastige Sachen und vServer erst recht völlig ungeeignet.
 
......

-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.0.18 i686

/usr/bin/tuning-primer.sh: line 388: bc: command not found
/usr/bin/tuning-primer.sh: line 389: bc: command not found
/usr/bin/tuning-primer.sh: line 390: bc: command not found
/usr/bin/tuning-primer.sh: line 391: bc: command not found
/usr/bin/tuning-primer.sh: line 392: bc: command not found
/usr/bin/tuning-primer.sh: line 393: bc: command not found
Uptime = days hrs min sec
Avg. qps = 6
Total Questions = 514064
Threads Connected = 1

Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations

To find out more information on how each of these
runtime variables effects performance visit:
MySQL AB :: MySQL 5.0 Reference Manual :: 5.1.3 System Variables
Visit MySQL AB :: MySQL Enterprise Advisors
for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES
Current long_query_time = 10 sec.
You have 0 out of 514076 that take longer than 10 sec. to complete
The slow query log is NOT enabled.
Your long_query_time may be too high, I typically set this under 5 sec.

WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 3
Historic threads_per_sec = 0
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size

MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 1
Historic max_used_connections = 8
The number of used connections is 8% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

MEMORY USAGE
/usr/bin/tuning-primer.sh: line 1164: bc: command not found
/usr/bin/tuning-primer.sh: line 1165: bc: command not found
/usr/bin/tuning-primer.sh: line 1189: bc: command not found
/usr/bin/tuning-primer.sh: line 1192: bc: command not found
/usr/bin/tuning-primer.sh: line 1193: bc: command not found
/usr/bin/tuning-primer.sh: line 1195: bc: command not found
/usr/bin/tuning-primer.sh: line 1197: [: -gt: unary operator expected
/usr/bin/tuning-primer.sh: line 350: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 362: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 369: export: `0=max_memoryHR': not a valid identifier
Max Memory Ever Allocated : bytes
/usr/bin/tuning-primer.sh: line 350: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 362: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 369: export: `0=per_thread_buffersHR': not a valid identifier
Configured Max Per-thread Buffers : bytes
/usr/bin/tuning-primer.sh: line 350: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 362: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 369: export: `0=global_buffersHR': not a valid identifier
Configured Max Global Buffers : bytes
/usr/bin/tuning-primer.sh: line 350: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 362: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 369: export: `0=total_memoryHR': not a valid identifier
Configured Max Memory Limit : bytes
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Physical Memory : G
Max memory limit seem to be within acceptable norms

KEY BUFFER
/usr/bin/tuning-primer.sh: line 331: bc: command not found
/usr/bin/tuning-primer.sh: line 612: bc: command not found
/usr/bin/tuning-primer.sh: line 613: bc: command not found
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current MyISAM index space = M
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current key_buffer_size = M
Key cache miss rate is 1 : 89
Key buffer fill ratio = %
/usr/bin/tuning-primer.sh: line 646: [: -ge: unary operator expected
/usr/bin/tuning-primer.sh: line 650: [: -ge: unary operator expected
/usr/bin/tuning-primer.sh: line 654: [: -le: unary operator expected
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size

SORT OPERATIONS
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current sort_buffer_size = K
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current record/read_rnd_buffer_size = K
Sort buffer seems to be fine

JOINS
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current join_buffer_size = K
You have had 6556 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.

Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.

OPEN FILES LIMIT
Current open_files_limit = 1024 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_cache value = 64 tables
You have a total of 912 tables
You have 64 open tables.
Current table_cache hit rate is 0%, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current max_heap_table_size = M
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current tmp_table_size = M
Of 16622 temp tables, 37% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
/usr/bin/tuning-primer.sh: line 331: bc: command not found
Current read_buffer_size = K
Current table scan ratio = 38 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 2834
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
Click to expand...




Hilfe? Was kann ich jetzt tun?
 
Falls die o.g. Domain auf Deinem Server liegt verwendest Du SuSE. Bei SuSE heißt das am häufigsten verwendete Paketverwaltungssystem "Yast". Lies Dir mal die Anleitungen zur Paketverwaltung - openSUSE im OpenSuSE-Wiki durch. Da erfährst Du dann auch, dass Du in Yast unter dem Punkt Softwareverwaltung das Paket "bc" auswählen und dann automatisch installieren kannst.

Bevor Du Dich anschließend daran machst, das "Chaos"-Problem zu lösen, solltest Du dringend Deine Linux-Kenntnisse auf ein akzeptables Niveau bringen, damit Du auch die Fähigkeiten hast, Deinen Server adäquat zu administrieren. Zumindest solltest Du ihn sicher konfigurieren können und die Softwareinstallation immer auf dem aktuellsten Stand halten (Stichwort: Sicherheitsupdates) -- schon allein dafür musst Du mit der Paketverwaltung des Systems umgehen können.

Viele Grüße,
LinuxAdmin

PS: bc ist ein kommandozeilenbasierter Rechner
 
ja wie, ich kann ja nur über die konsole (ssh) meinen server administrieren, wenns um ein locales linux ginge wär da weniger das problem. oder kann ich irgendwie per remote auf den server zugreifen???
 
omg sorry für meine blödheit ^^
bc ist jetzt installiert... werde mal neuen test laufen lassen

EDIT


Ergebisse:

-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.0.18 i686

Uptime = 1 days 21 hrs 37 min 48 sec
Avg. qps = 5
Total Questions = 850360
Threads Connected = 1

Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations

To find out more information on how each of these
runtime variables effects performance visit:
MySQL AB :: MySQL 5.0 Reference Manual :: 5.1.3 System Variables
Visit MySQL AB :: MySQL Enterprise Advisors
for info about MySQL's Enterprise Monitoring and Advisory Service

SLOW QUERIES
Current long_query_time = 10 sec.
You have 0 out of 850372 that take longer than 10 sec. to complete
The slow query log is NOT enabled.
Your long_query_time may be too high, I typically set this under 5 sec.

WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 2
Historic threads_per_sec = 0
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size

MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 1
Historic max_used_connections = 9
The number of used connections is 9% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

MEMORY USAGE
Max Memory Ever Allocated : 32 M
Configured Max Per-thread Buffers : 155 M
Configured Max Global Buffers : 18 M
Configured Max Memory Limit : 174 M
Physical Memory : 1.47 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 140 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 109
Key buffer fill ratio = 11.00 %
Your key_buffer_size seems to be too high.
Perhaps you can use these resources elsewhere

QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size

SORT OPERATIONS
Current sort_buffer_size = 512 K
Current record/read_rnd_buffer_size = 508 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 8394 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.

Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.

OPEN FILES LIMIT
Current open_files_limit = 1024 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_cache value = 64 tables
You have a total of 912 tables
You have 64 open tables.
Current table_cache hit rate is 0%, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 28570 temp tables, 38% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
Current read_buffer_size = 252 K
Current table scan ratio = 34 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 2643
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
Click to expand...
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top