Why is Spring MVC's asynchronous mode more efficient than Synchronize?

since the purpose of asynchronism is to improve throughput, assuming a machine has a maximum of 1000 threads, what is the difference between async mode (DefferedResult) (tomcat threads) for handling requests and async mode (taskexecutor of spring) for callbacks?

what"s the difference between async mode and Synchronize mode 1000 threads?


I understand that the problem solved by springmvc (Asynchronous servlet) is that A large number of time-consuming operations fill up thread resources, causing the server to refuse to connect . It is not more efficient, because the operation you should deal with still has to be handled, and its IO is still Synchronize, so it cannot save thread resources for IO like reactor+IO multiplexing.
so what he can do is not to deny service because he is full of threads when dealing with long operations, because there are always 500threads to accept requests

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1e44629-44aac.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1e44629-44aac.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?