Timeline for Sitecore virtual user vs Session
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2017 at 10:47 | comment | added | Richard Hauer | I think the decision about virtual users is still about how much personalisation and reporting info you need to handle. You will definitely need a custom authentication and authorisation system, and it will have to be very high performance - a MongoDB collection with appropriate indexing in a good start; session backed by Redis with careful management of the session data will help too | |
| Feb 8, 2017 at 10:45 | comment | added | Richard Hauer | 500 concurrent, logged in users is still a lot. Don't forget that session timeouts are generally 20 minutes, so if a normal user session is 5 minutes you will have several thousand sessions in memory at any time - this could be gigs of memory. You definitely need proper out-of-process session handling and several Sitecore servers for this; maybe 2 quad-cpu or 3 dual-cpu boxes with 8-16GB RAM each. 1/2 | |
| Feb 7, 2017 at 6:38 | comment | added | Shailesh | just to clear the doubts their are 500k named users but yes concurrently the max number of logged in users max out at 500. Is it still a good choice of implementaion? | |
| Feb 6, 2017 at 16:49 | history | answered | Richard Hauer | CC BY-SA 3.0 |