Tell me, have you ever get any problem with slow member login?
I'm planning to use Umbraco for a website with about 200k members and I'm worried about the performance to log in members on the site.
I know it starts get slowy on the Umbraco admin, but, its ok because there we have a search and a alphabetical segregation. But when we turn to the front, (to the site you know?) do we get some slowness login?
Just wondering if you ever get though that situation. I mean, do Umbraco iterate in all members when it is about to sign in somebody?
Login will be a sql query and i can say with certainty that the membership code which is based on windows membership provider will NOT do something crazy like select * from members then loop each one till it finds a match! So it will not be slow logging in.
However one word of caution if after logging in you are going to get member properties and display them eg member name then do not keep doing new Member() in code because if you do and you want to display member properties in more than one place and each time you new Member you will get performance issues I worked on a site a while back and the dev had written code like that instead of just getting the member once he was doing a new member each time.
I would make use of the member index so you can use examine search which is a wrapper around lucene. You wont use it for login only to get member data that will be lightening quick and will not make db calls.
200K+ Members can make the LOGIN slow?
Hey People,
Tell me, have you ever get any problem with slow member login?
I'm planning to use Umbraco for a website with about 200k members and I'm worried about the performance to log in members on the site.
I know it starts get slowy on the Umbraco admin, but, its ok because there we have a search and a alphabetical segregation. But when we turn to the front, (to the site you know?) do we get some slowness login?
Just wondering if you ever get though that situation. I mean, do Umbraco iterate in all members when it is about to sign in somebody?
Wallas,
Login will be a sql query and i can say with certainty that the membership code which is based on windows membership provider will NOT do something crazy like select * from members then loop each one till it finds a match! So it will not be slow logging in.
However one word of caution if after logging in you are going to get member properties and display them eg member name then do not keep doing new Member() in code because if you do and you want to display member properties in more than one place and each time you new Member you will get performance issues I worked on a site a while back and the dev had written code like that instead of just getting the member once he was doing a new member each time.
Regards
Ismail
Hey Ismail, tks for your answer.
I found that situation http://our.umbraco.org/forum/developers/api-questions/5647-GetProperty-on-a-member-object-slow. He's using caching for doing that.
The version i'm using is 4.7.1. Do you know if this problem may affect my solution as well? Is caching the best way of solving this problem?
Wallas,
I would make use of the member index so you can use examine search which is a wrapper around lucene. You wont use it for login only to get member data that will be lightening quick and will not make db calls.
Regards
Ismail
Ah GREAT! I was a little bit confuse with that! Thank you for cleaning this mess out Ismail!
Best Regards,
Wallas
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.