Foros del Web » Administración de Sistemas » Software para Servers »

Mejorar el consumo de recuros en vps?

Estas en el tema de Mejorar el consumo de recuros en vps? en el foro de Software para Servers en Foros del Web. Necesito ayuda para mejorr elp erfomance de un vps debian a 64 bits con 2gb de ram y 2 ghz de cpu en leaseweb. la ...
  #1 (permalink)  
Antiguo 04/04/2012, 19:54
 
Fecha de Ingreso: enero-2005
Mensajes: 95
Antigüedad: 19 años, 10 meses
Puntos: 0
Mejorar el consumo de recuros en vps?

Necesito ayuda para mejorr elp erfomance de un vps debian a 64 bits con 2gb de ram y 2 ghz de cpu en leaseweb. la web carga lento cuando eluso de cpu de apache sube al 30%,ademas el cpu no baja del 90%,no se nada de administracion de vps, leyendo vi que al ejecutar el comando top puedo ver los procesos que se estan ejecutando.estos son mis resultados

y en el panel el cosnumo de apache em sale esto

mi sitio web(no coloco el sitio por que infringe las politicas de la web) tiene unas 200 visitas cuando ocurre eso, pero cuando estuve en otro vps lso 200 usuarios los aguantaba sin problemas.

Se que hay que configurar el apacge.conf y my.cnf pero no se que parametros debo tocar ni que valores debo colocar.este es mi apache.conf

Código:
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "foo.log"
# with ServerRoot set to "/etc/apache2" will be interpreted by the
# server as "/etc/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

##
## Server-Pool Size Regulation (MPM specific)
## 

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
    StartServers          2
    MinSpareServers       3
    MaxSpareServers      10
    MaxClients          30
    MaxRequestsPerChild   1000
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
#              graceful restart. ThreadLimit can only be changed by stopping
#              and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
    StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75 
    ThreadLimit          64
    ThreadsPerChild      25
    MaxClients          150
    MaxRequestsPerChild   1000
</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
    StartServers          2
    MaxClients          150
    MinSpareThreads      25
    MaxSpareThreads      75 
    ThreadLimit          64
    ThreadsPerChild      25
    MaxRequestsPerChild   0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#

AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain


#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

# Include module configuration:
Include mods-enabled/*.load
Include mods-enabled/*.conf

# Include all the user configurations:
Include httpd.conf

# Include ports listing
Include ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
Include conf.d/

# Include the virtual host configurations:
Include sites-enabled/
GracefulShutDownTimeout 3
AddOutputFilter INCLUDES .shtml
AddType text/html .shtml
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps
ojalame puedan hechar la mano, por que leo y leo pero en cada sitio sale diferente informacion y no se cual debo aplicar a mi vps
__________________
customsmf
Seo,tutoriales,decargas
  #2 (permalink)  
Antiguo 05/04/2012, 19:54
 
Fecha de Ingreso: agosto-2008
Ubicación: Colombia
Mensajes: 342
Antigüedad: 16 años, 3 meses
Puntos: 24
Respuesta: Mejorar el consumo de recuros en vps?

Desafortunadamente no existe una opción generalizada para casos como el tuyo, lo ideal sería que un admnistrador de servidores lo chequeara y hiciera los ajustes correspondientes. logicsupport, infranetworking, ultimateservermangement, te pueden echar una mano.
  #3 (permalink)  
Antiguo 05/04/2012, 20:21
 
Fecha de Ingreso: enero-2005
Mensajes: 95
Antigüedad: 19 años, 10 meses
Puntos: 0
Respuesta: Mejorar el consumo de recuros en vps?

tal vez sirva de algo,el sistema de foros que uso es smf. es bien raro por qu hasta con menos visitas de antes ahora el servidor se cuelga
__________________
customsmf
Seo,tutoriales,decargas
  #4 (permalink)  
Antiguo 06/04/2012, 13:41
 
Fecha de Ingreso: febrero-2012
Ubicación: México
Mensajes: 227
Antigüedad: 12 años, 9 meses
Puntos: 48
Respuesta: Mejorar el consumo de recuros en vps?

Es muy raro que mysql consuma tantos recursos. Apache no parece ser el problema.

Tienes mucha memoria, asi que podrias aumentar la memoria cache de mysql para que guarde las consultas mas comunes.
  #5 (permalink)  
Antiguo 06/04/2012, 14:49
 
Fecha de Ingreso: enero-2005
Mensajes: 95
Antigüedad: 19 años, 10 meses
Puntos: 0
Respuesta: Mejorar el consumo de recuros en vps?

GRacias eres un genio!! eso confirma tambien lo qu ehice probando con el mysqltuner.pl, parece que estaba buscando pro el lado equivocado, en las recomendacionesl del script me salio que debia cambiar este valo
query_cache_size = 32M
lo deje tal como se muestre,estaba en 16mb, y ahora el uso de cpu bajo drasticamente,recien ha vuelto a subir,pero desde que hice el cambio no ha subido a mas de 50%,solo el uso de cu de apache sigue alto,pero ya no sube hasta 117%,ya me diste uan luz de que es el mysql el que debo optimizar,con razon y en el utlmo vps tuvieron que darnos un procesador de 4 nucleos para que mejorara la carga,todo por no saber....te agradezco la ayuda
__________________
customsmf
Seo,tutoriales,decargas
  #6 (permalink)  
Antiguo 07/04/2012, 02:58
Avatar de ciscoh4x0r  
Fecha de Ingreso: junio-2010
Ubicación: Londres, Inglaterra
Mensajes: 300
Antigüedad: 14 años, 4 meses
Puntos: 12
Respuesta: Mejorar el consumo de recuros en vps?

Solo de entrada... Podrias evitar usar bases de datos innodb y veras una gran diferencia.
__________________
Algún día habrá una persona mejor que yo, pero esa persona no eres tú, ni ese momento es ahora...

Etiquetas: apache, consumo, ip, mejorar, php, red, server
Atención: Estás leyendo un tema que no tiene actividad desde hace más de 6 MESES, te recomendamos abrir un Nuevo tema en lugar de responder al actual.
Respuesta




La zona horaria es GMT -6. Ahora son las 14:20.