Hi Josh,

Umbraco creates separate Lucene indexes for nodes and for members so it's not a problem for performance. You can create your own index with properties or use standard.

<IndexSet SetName="InternalMemberIndexSet" IndexPath="~/App_Data/TEMP/ExamineIndexes/InternalMember/">
    <IndexAttributeFields>
      <add Name="id" />
      <add Name="nodeName"/>
      <add Name="updateDate" />
      <add Name="writerName" />
      <add Name="loginName" />
      <add Name="email" />
      <add Name="nodeTypeAlias" />
    </IndexAttributeFields>
  </IndexSet>

Thanks, Alex

Hi Alex,

Excellent! Good to know.

Thanks, Josh

What version of v7 are you using? In 7.1 there is a Umbraco.TypedMember helper, but in 7.0 there isn't. This means that even though examine is used if you fetch members in v7 it might not use Examine and could still be very slow. In Umbraco the more properties you add the slower it will become. 7.1 has a new member API with better performance, but it can still become slow.

Jeroen

You could have a look at uMembership if the performance isn't good enough.

Jeroen

Thanks Jeroen. I am on 7.0.2 right now, but I will be moving to 7.1 soon. I haven't done any real-world testing yet so I may be a bit premature with my performance concerns, but it is good to know that there may be some options if performance is a bit slow.

Cheers to all!

is working on a reply...