LiteSpeed Enterprise with Woocommerce Performance very Bad

#1
Hello we use Woocommerce in all our 10 Onlineshops. We have more as 10k Products Single and Variable Products.
Test to Open the Store https://xfunshop.com the first side Load Quick but when you click on a Product then it need very very very long more as 40 Secunds or Server Timeout.

What did we do all:
Stop all Plugins bit of Woocommerce and the Mollie or Stripe Payment Plugin nothing change still Slow
Upgrade our Dedicated Server System to 20 Real Cores and 256GB DDR4 + 2TB SSD but nothing same effect
We use Cloudflare as Cache and CDN Solution.
JetPack as Image CDN
WP-Optimize Premium for Cache and Minimize
Ligtspeed Server Enterprise ( Ligtspeed Cache we have Test more Slow )
Redis not really Help make all more Slow

So we need help we lose money about our Customers not wanna wait 40 Secunds of one Product.
 

serpent_driver

Well-Known Member
#2
Wrong shop software for this high number of items. I have shops running with > 500.000 items on a VPS and it flies. No CDN (cache), no DB cache. Only LiteSpeed with LScache.
 
#3
Hmmmmm What is wrong on Woocommerce the Woocommerce Support say self with 1000000 Products is no Problem. Can it be that i have do something wrong in the MariaDB ?? About so how i have read is that every Product Page will build from the Database so baybe i configure the Database Wrong and she is Slow
 
#5
user = mysql
pid-file = /run/mysqld/mysqld.pid
socket = /run/mysqld/mysqld.sock
#port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
max_allowed_packet = 32G
max_connect_errors = 100000

performance_schema=ON
performance-schema-instrument='stage/%=ON'
performance-schema-consumer-events-stages-current=ON
performance-schema-consumer-events-stages-history=ON
performance-schema-consumer-events-stages-history-long=ON

bind-address = 127.0.0.1
max_connections = 400
log_error = /var/log/mysql/error.log
expire_logs_days = 10
character-set-server = utf8
collation-server = utf8_general_ci

tmpdir = /tmp
user = mysql

default_storage_engine = InnoDB
innodb_buffer_pool_instances = 100 # Use 1 instance per 1GB of InnoDB pool size
innodb_buffer_pool_size = 64G # Use up to 70-80% of RAM
innodb_file_per_table = 1
innodb_flush_log_at_trx_commit = 0
innodb_flush_method = O_DIRECT
innodb_log_buffer_size = 8G
innodb_log_file_size = 8G
innodb_stats_on_metadata = 0


innodb_thread_concurrency = 10
innodb_read_io_threads = 256
innodb_write_io_threads = 128

query_cache_limit = 512M # UPD - Option supported by MariaDB & up to MySQL 5.7, remove this line on MySQL 8.x
query_cache_size = 128M # UPD - Option supported by MariaDB & up to MySQL 5.7, remove this line on MySQL 8.x
query_cache_type = 1 # Option supported by MariaDB & up to MySQL 5.7, remove this line on MySQL 8.x

key_buffer_size = 128M # UPD

low_priority_updates = 1
concurrent_insert = 2

back_log = 512
thread_cache_size = 100
thread_stack = 32M

interactive_timeout = 900
wait_timeout = 900

join_buffer_size = 40M # UPD
read_buffer_size = 32M # UPD
read_rnd_buffer_size = 32M # UPD
sort_buffer_size = 32M # UPD


table_definition_cache = 40000 # UPD
table_open_cache = 40000 # UPD
open_files_limit = 60000 # UPD - This can be 2x to 3x the table_open_cache value or match the system's

max_heap_table_size = 32G
tmp_table_size = 32G

ft_min_word_len = 3 # Minimum length of words to be indexed for search results

quick
quote_names
 
Top