Click here to Skip to main content
15,799,363 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hello all,

I want to share my experience on a distributed system and the challenge that we faced as a team. We have built a web-application that is managed centrally. Installed and runs off from a central server - works fine or does what is expected in terms of functionality. However, we are being challenged on performance issues. We are getting network latency - before our new web-application gets deployed, there is a legacy standalone or desktop system that runs on multiple branches and states as a distributed system. The legacy does not have a performance issue because the application and database are on the same local network.

However, for the centralized application which is the new one, we have identified that some branches are slow, and we also have identified mainly because of the network issue but we have to overcome the problem at the same time. We are getting slow response times for some reports and/or requests.

What options do we have to give as a solution(s) for these poor performance sufferings?


What I have tried:

caching using redis, query optimization, and reduced chatty requests and used dapper
Updated 30-Mar-21 3:27am
Gerry Schmitz 30-Mar-21 11:42am    
Before trying to fix "slow", you need to identify "why" slow. You haven't. You're trying to fix a "problem" you don't understand. Not possible.
Yonathan1111 2-Apr-21 7:26am    
Okay, I thought I was clear on my statement, but here I will try to explain more what we identified so far as our main performance problem.
1. Network Latency: This is the major and known problem that we have because many branches are performing seamlessly or their response time is acceptable for users as well as it is matching the standards.
2. Query: This is another area where we are working as a team there are some queries that need to be optimized.

We are not guessing nor
Dave Kreskowiak 30-Mar-21 12:47pm    
The legacy does not have a performance issue because the application and database are on the same local network
NEVER make that assumption. So what if they are on the same network? Proper design of your database, app, and any middleware is what lends to the performance of the overall app, not just "it's all on the same network".

You're going to have to instrument your code and get profilers looks at every aspect of your entire application, end-to-end, to see where the bottlenecks are and what the impacts to your application are.
Yonathan1111 2-Apr-21 7:35am    
Hi, I did not make any assumptions, we have tested our system within the local area network and it performed well and the legacy system does not have any performance problem.
The problem comes when users use ours from a different network due to two or three cases as I have mentioned under the above comment.
Dave Kreskowiak 2-Apr-21 10:53am    
There is so much that can impact your app performance that's it impossible to tell you specifically what to look at.

You're going to have to look at EVERYTHING between the client machine and your servers, wherever they may be.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900