Home › Forums › Legacy Support › Support queries › Update Issues › Not able to support 100 concurrent users
Tagged: Concurrent users
- This topic has 19 replies, 3 voices, and was last updated 3 years, 8 months ago by jatin1malhotra.
-
AuthorPosts
-
February 8, 2021 at 5:34 pm #338821jatin1malhotraParticipantHello Team, We are Not able to support 100 concurrent users. For every login it consumes 1% of the 8GB RAM. So technically, I can't run 100 concurrent users. I'm using this plan on AWS Lightsail - 8 GB RAM, 2 vCPUs, 160 GB SSD. My wordpress is hosted via plesk tool. Observations so far : 1) Configuration : Wordpress via Plesk on AWS Lightsail - 8 GB RAM, 2 vCPUs, 160 GB SSD 2) I ran a load test of 1000 clients over 15 secs. Results - https://bit.ly/344nD2w. CPU Usage goes upto 90% 3) I used Jmeter to load test signups of around 50 users within 2 minutes. Result - CPU Usage goes upto 85% on average and RAM upto 50% Please guide, how do we optmise. The results from this activity will really help you cater other customers who want WPLMS to be highly scalable. Request to please help me. Please let me know your observations on how can we optimise. Urgent.February 9, 2021 at 5:30 pm #339070MrVibeKeymaster1. The bottle neck will be mysql , I would suggest you to keep a different server for mysql which can be scaled up as per requirements. 2. The authentication happens once, so you're testing the login scenario which runs the wp-authenticate hook, if there is any security plugin it will run here. 3. The authentication is done once and token is generated for the expiry period that you set in WP admin - Vibebp - settings [ along with refresh token in the user object ] Login load can be distributed because the users may not login at once. Even if they login, repeat logins will depend on your settings. The bottleneck IMO will be quiz submission for which we have this solution coming up : https://trello.com/c/HmgOp6TAFebruary 9, 2021 at 7:09 pm #339086jatin1malhotraParticipantThis reply has been marked as private.February 9, 2021 at 7:12 pm #339088jatin1malhotraParticipantThis reply has been marked as private.February 9, 2021 at 9:55 pm #339110jatin1malhotraParticipantRegarding login, I did a bulk signup of 100 different accounts & the system consumed lof resources, can we please try to address the base query of how do we ensure atleast 100 concurrent users on a 8GB Ram server. Please guide.February 10, 2021 at 3:04 pm #339313MrVibeKeymasterThat is quite expected, the signup will send emails and make entry in the database 1. Use an external mail server (smtp.com with postman smtp WP plugin) 2. Optionally use a different Mysql server.February 11, 2021 at 2:08 pm #339584jatin1malhotraParticipantThis reply has been marked as private.February 14, 2021 at 10:38 am #340097jatin1malhotraParticipantCan you please guide.February 14, 2021 at 6:31 pm #340129jatin1malhotraParticipantThis reply has been marked as private.February 15, 2021 at 3:27 pm #340329Anshuman SahuKeymasterPlease test it by having the 100 users already signed up on the site . there is no such case that 100 user may signup at the same moment .February 15, 2021 at 8:40 pm #340379jatin1malhotraParticipantThis reply has been marked as private.February 15, 2021 at 8:43 pm #340380jatin1malhotraParticipantAlso, my query is I m not able to support 1000 non logged in concurrent users on the siteFebruary 16, 2021 at 3:43 pm #340628MrVibeKeymasterI think the bottle neck in your case is the "emails" not the database entries. So you need an email relay server. here's what you need to do : Free method : Setup emails using third party email server and confgiure in wordpress , one example : https://wpforms.com/how-to-set-up-wordpress-smtp-using-amazon-ses/ -- paid & easier version. : for me SMTP.com is easier, so you can install WP Postman SMTP and add the SMTP.com api key to account. -- for 1000 non logged users, cache everything in your site. Install WP Rocket and cache the entire site, except for the PWA page where user's will login when BP Single mode is enabled.February 17, 2021 at 3:35 pm #340847jatin1malhotraParticipantThis reply has been marked as private.February 17, 2021 at 6:58 pm #340883jatin1malhotraParticipantMy performance has improved a lot after W3 Total cache for non logged in user. Can you please help me understand how do I optimise performance for logged in user(since they are not advised to be cached), since we have 100% cpu utilisation with just 10 logged in users. Please guide.
-
AuthorPosts
- The topic ‘Not able to support 100 concurrent users’ is closed to new replies.