Can IIS be configured so that, for example, the same request is cached for 10 minutes and the saved HTML is returned to the user instead of a new call to PHP (or other interpreters)?

If the answer is yes, then what will happen if different data should be output to the same URL (HTTP authentication / cookie / session)?

Detailed description of the problem: IIS Bundle (intracorporate server on Windows 4 Xeoni kernels on 2.67 Ghz + 6gb ozu) + PHP Fast-CGI. Laravel website. Problem: if 100-150 people visit the site at the same time, everything hangs. I noticed that already at ab -c 10 the CPU load becomes 100%. I decided to fix it. Put the opcache. Requests from the database itself are cached. Here I look, how else to cache.

  • describe the whole picture. What you want to cache and why. What frameworks, etc. used in the app - teran
  • @teran IIS Bundle (internal corporate server on Windows 4 Xeon 2.67 Ghz + 6gb oz kernel) + PHP Fast-CGI. Laravel website. Problem: if 100-150 people visit the site at the same time, everything hangs. I noticed that already at ab -c 10 the CPU load becomes 100%. I decided to fix it. Put the opcache. Requests from the database itself are cached. Here I look, how else to cache. - GroZa
  • it is better to add the above to the question text, and add the laravel tag. wincache still try to add besides opcache - teran
  • DBMS on the same server or on a separate? - teran
  • @teran DBMS on a separate server. On the contrary, 100 loading occurs when you perform light requests without referring to the database. Xdebug showed that Lara ships about 300 files as autoloads. Can wincache and opcache work together? - GroZa

0