Question

I have 3 mariadb galera db s, 2 nginx/php machines at these sizes DBs - E8ds_v5, nginx/php-fpm - D4ds_V5 I am getting really bad performance from mariadb. These machines are in the same vnet, but different subnets for db and web. The two nginx/php-fpm servers share web files through and azure files premium nfs share which seems to be working OK.

我试图将银行的储存升级到P40,但业绩没有变化。目前,对E20ds_v5进行测试(仅测试一个服务器),储存在SSDv2 (30 000 IOPS, 500 MB/s)上

I am running wordpress benchmarks and timing db queries to a barebones wordpress install with absolutely no change in score no matter what is done. The barebones wordpress install is pointed directly to the upgraded machine at the moment. My next step is to try and use MySQL Flex, but it would be great if I could get this self hosted mariadb working.. no matter what amount of tuning is done, things seem to remain the same, slow.

I think the biggest problem is that I get terrible performance if MySQL is not running locally to where PHP is being processed.

Galera DB INFO requested

这里是的基准分。带有不同构造的口头标本:。

Benchmark of nginx/php-fpm/mariadb on the same VM (Standard_D1_v2) - NODATA

Benchmark of nginx/php-fpm/mariadb on the same VM (Standard_D1_v2) - WITH DATA

https://imgur.com/M3PZ6Rt”rel=“nofollow noreferer”> 在使用2台NGIssel/PHP-FPM服务器时,有1台单独的MySQL 8 FLEX DB(别名次网) Business Critical, E16ds_v5, 16 vCores, 128 GiB RAM, 256 GiBstor DATA

When using 2 NGINX/PHP-FPM servers with 1 separate MySQL 8 FLEX DB (different subnet) Business Critical, E16ds_v5, 16 vCores, 128 GiB RAM, 256 GiB storage DATA

https://imgur.com/O2dHzNS”rel=“nofollow noreferer”> 在使用上述2台NGIssel/PHP-FPM服务器和3台dbs(加拉,不同网络的子网)时,DATA

When using 2 NGINX/PHP-FPM servers with 1 maria db (same subnet) mentioned above NO DATA

Answer 1

问题被证明是缓慢的Landres NFS系统。尽管这是NFS 4.1文档库,但太慢。

我们建造了自己的HANFS服务器,并且该机在加莱拉银行方面遇到问题。

Answer 2

Per Second = RPS

四. 关于考虑为“服务器”门户网站、环境、参数提出的建议

innodb_buffer_pool_size=24G  # from 48G until more than 10G is used
thread_pool_size=6  # from 16 you only have 8 cpu s 
read_rnd_buffer_size=16384  # from 4M to reduce innodb_data_read RPS of 114,229 
read_buffer_size=524288  # from 3M to reduce innodb_data_read RPS of 114,229 
innodb_lru_scan_depth=100  # from 1024 to reduce 90% CPU cycles used for function.

有更多的机会改善业绩。请见我的简介。

Observation, innodb_secondary_index_triggered_cluster_reads had 1,878,540 reported in 16 hours. This is usually caused by table(s) with NO Primary Key. For a query to find the tables of this nature, please provide an email address.

友情链接