Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bernabauer/www.bernabauer.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Otimizando seu servidor virtual para WordPress – bernabauer.com

Otimizando seu servidor virtual para WordPress

Semana passada vi um tweet do Bruno Alves informando seu feito em otimização do servidor virtual para funcionar com Apache, WordPress. Curioso para saber como ele conseguiu medir os 2700 requisições por segundo, disparei a pergunta óbvia. A resposta veio a galope.

comando: “ab -c 100 -n 10000 http://site.com/” diminua o c e o n para 10 e 100 no começo. Normal wp+apache ± 3-7

Depois de executar o comando fazendo os ajustes recomendados pelo Bruno, creio que finalmente descobri por que meu Apache costuma capotar de vez em quando. A quantidade de acessos simultâneos é superior ao que meu VPS e configurações do WordPress consegue lidar e por isto o maldito pede água.

Como resolver eu ainda não sei, mas fico feliz que aprendi um novo comando que ajuda a fazer o papel de sysadmin. Vou ler depois com calma o guia de otimização de VPS para o WordPress para ver se consigo melhorar a performance, mas isto vai ser mais tarde quando eu tiver mais tempo.


Publicado

em

por

Comentários

Deixe um comentário

O seu endereço de e-mail não será publicado. Campos obrigatórios são marcados com *