|
<< Click to Display Table of Contents >> Navigation: Telegram > 2023 > 10 > 03 > Telegram_2023-10-03T02 |
2023-10-03T02:00:35
the problem the way I have already experienced is: Your Web server can handle 1000 requests per second, but your DB can't handle not even 100 queries per minute.
2023-10-03T02:01:40
queries poorly written, high latency, no indexes, tables/queries returning too many records
2023-10-03T02:02:33
I am using index
2023-10-03T02:03:04
yes, I know you have indexes. But sometimes the specific query is causing a full table scan. That's slow
2023-10-03T02:03:29
but the application running fine one soundly become slow
2023-10-03T02:04:13
like today the complain from the application very slow alter i restart server goes ok
2023-10-03T02:05:54
so... You need to check something: when the application is slow, is the DB server responding quickly?
2023-10-03T02:06:09
there for i wand add to my application check network response to alert the end user that problem comes from network
2023-10-03T02:06:22
second, if the app is slow, you need to check if there is something keeping it from responding
2023-10-03T02:07:14
It is not possible to avoid all types of deadlocks and such errors
2023-10-03T02:07:28
I mean, through code inspection
2023-10-03T02:07:36
before start up server the response time was 7.86 seconds after restart become 0.75 second
2023-10-03T02:07:47
yes
2023-10-03T02:08:31
Next time it happens, open the task manager and look at all the cores activity. See if one of them (or more) are locked in 100%
2023-10-03T02:10:04
few days working well then one it become slow
2023-10-03T02:10:42
These days I am try to improve performance of my application
2023-10-03T02:12:01
Yes, the secret for a good app is performance, from the bottom up. That's what I've been doing with IW since 2012
2023-10-03T02:13:02
Some parts of IW code today performs 20x faster than it use to ??