Activities of "liaquathussain"

Hi,

Sorry for late reply, I was away.

Following is access detail.

https://app.speedautosystems.com Company Code (Tenant Code): BelhasaTest Username: admin Password: admin123

DB is already tunned properly, infact it is auto tunned by Azure and indexes are created reqularly, DB response and queries running is fine if excute some query directly.

Question is, why app gone slow after upgrade.

Before upgrade we were using following plan for azure Azure Web App 1 Large Intance Azure DB Standard (S3) 100 DTU Utilization and app response was ok

After upgrade we have to increase resources as app was totally stuck Azure Web App 2 Large instances Azure DB Standard (S4) 200 DTU Even doubling resources, app response is considerable slow than previous one. Earlier we were not having any complaints from our customers now we do have frequent complains

Also breaking abp/aspzero related data loading to module basis is very important as it works following.

"On startup, as dynamic web api is created, js proxies are generated, all permissions and localization data is loaded, all js files are bundled and loaded once,"

Is there any way to

1. instead of dynamic web api generation we can have while building solution to avoid runtime time consumption?
2. Is there any way to break permissions and localization data to modules and for specific module only that part should be loaded?
3. Is there any way to generate js proxies based on group of app services so that only module specific js should be created?

You valuable suggestion will help us to get it fined tunned as our app is growing day by day, features are increasing, tenants are increasing.

Thanks you!

Thanks cangunaydin your solution is working

if i choose to create my own repository implementation where would i register the Context Dependency and where should the context be kept in EntityFramework project or Some other project?

yes i have a 2nd db context and as I have already mentioned that I am using a third party database so, I am unable to go with Code first approch. even if I choose to go with code first somehow(i know Its not suitable in this scenario). I would have to face same problem

I would not be able to use Repositories as it requires IEntity Interface to be implemented and IEntity has an Id property to be used as primary key. which cannot be ensured that other database must be using a column with name Id as primary key.

here is an example of entities from other dbContext

public partial class Location { public string Code { get; set; } // primary key in this case public string Description { get; set; } public decimal StSpotAgmtNo { get; set; } ... }

thank you Windows Azure does not support MSDTC yet. any workaround for that ?