Replies: 2 comments 3 replies
-
DT mirrors the NVD. The modified feed is only valid for seven days. Therefore DT will pull down all yearly feeds every six days. Expect a spike every six days to account for the hundreds of thousands of records it needs to replicate. Interrupting this process will cause problems. A properly tuned DT and DB server should be able to mirror in under an hour. If it takes longer than that you'll likely need to switch to an instance that is optimized for compute and memory. |
Beta Was this translation helpful? Give feedback.
-
Hi, @stevespringett. thanks for the explanation. I was wondering even after one hour why we don't get back to regular CPU consumption... Looking at the metrics, we can see on 04.19 CPU consumption started to increase and it never returns to normal consumption, only after a DT restart on 04.23. Here our configuration:
I'll monitor the next few days to see how it behaves. |
Beta Was this translation helpful? Give feedback.
-
Anyone experiencing DT high DB CPU consumption?
We noticed that at least once a week we are having these CPU spikes and we need to restart the DTApiServer….
This is my config:
Here some metrics from last two weeks:
Anyone facing the same problem? Any ideas on how to fix it?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions