MySQL burns almost the entire processor all the time. How to start diagnosing this problem? Here are the life statistics:
Our car:
Windows Server 2008 R2 Enterprise Intel G6950 2.80GHz 4GB RAM 64-bit MySQL Server 5.5 ASP.NET v2.0
From my.ini:
character-set-server=latin1 default-storage-engine=INNODB sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" max_connections=500 query_cache_size=256M table_cache=320 tmp_table_size=195M thread_cache_size=8 myisam_max_sort_file_size=100G myisam_sort_buffer_size=256M key_buffer_size=1024M read_buffer_size=64K read_rnd_buffer_size=256K sort_buffer_size=256k innodb_additional_mem_pool_size=12M innodb_flush_log_at_trx_commit=1 innodb_log_buffer_size=7M innodb_buffer_pool_size=1024M innodb_log_file_size=117M innodb_thread_concurrency=8 external-locking
The table that is most often accessed and seems to slow down is asset_search_asr
The following screenshots are the results that I get from running EXPLAIN:

AND SHOW THE INDEX:

Thanks in advance to everyone who is in no hurry to respond to the offer. I am a beginner, so even a general idea of ββwhat to look for will be of great help.
source share