Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
Another possibility would be to use an external service like blitz.io, stormforger.com or loadstorm.com to generate lots of traffic and concurrent users to your site.
I also use blitz.io, stormforger and loadstorm as Viktor already write. These tools are great for testing professionally from outside. Alternatives are JMeter or BeesWithMachineGuns
The server itself should easily be able to handle this, the question is more how you tune the Webserver and WordPress config. E.g. offloading static content to NGINX and using a WordPress caching solution like WP Rocket or WP Super Cache will increase the max amount of concurrent users. The bottleneck is usually the mysql database. The solution: reduce the amount of calls to the database. Afterwards reduce the amount of PHP processes that have to be started. And so on.
Yes, the server should be capable of doing it. As Jan already said, using internal cache (via a WP plugin) will help your server to handle it. If you want to go a step further, then you should think about a server-side caching mechanism such as Memcached or Varnish.
But you should first try it with the internal solution because this is easier to integrate and to manage.
Change servername to the correct name of your server.
See image for better understanding (hint: the number varies because one more connection was opened during I typed the command):
Regarding blitz.io:
I already asked the support team in January about this issue and they just said that they work on it and it will take some time. If it is still deactivated, then I think that you shouldn't wait for it...