Base solution for your next web application
Open Closed

How to remove Multi-Tenancy feature from code base? #6982


User avatar
0
dzungle created

Hello Support team, We use ASPNET Zero (Angular + ASP.NET Core) as the base solution for our web application deployed in our LAN. It’s great that your base solution saved us a lot of time, but the performance (response time) is a litle bit slow. We think the cause might be of the Multi-Tenancy feature (even we turned it off). We don’t need this fearture in our application. So, do you have any other version of ASPNET Zero without the Multi-Tenancy feature? If you don’t have, we need to remove Multitennancy feature from the code base. Is it possible to do that? Could you please show us steps to achieved this task. Thank you very much. Best Regards, Le Dzung


4 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team

    First of all, the multi-tenant code is built into the Abp framework and cannot be removed. It can only be disabled. Then I think the problem of slow response time is not like that caused by multi-tenancy.

    Can you elaborate on this performance issue?

  • User Avatar
    0
    dev_frontrush created

    Something you may also/should want to look at is your indexing within Sql Server. Using EF code first is great but if you have not done any additional performance reviews specifically on the db with indexing, you don't have a lot of index additions in your db context generator already, you will be very surprised (and happily so) when you do.

    Code first doesn't mean you don't need someone on the db performance tuning and is something that is constantly overlooked "hey, we use code first, we don't need a dba anymore" eghghgh!!!! mistake

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    I agree with @dev_frontrush, you might want to profile your queries with a tool to see if there are any missing indexes or if there are any improvement points on your DB.

  • User Avatar
    0
    dzungle created

    Thank you, my firends. We'll do some SQL server database tuning.