24 Jan 2025
	
		
		09:44 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - last edited on 
    
	
		
		
		27 Jan 2025
	
		
		07:00 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		
		
			MaciejNeumann
		
		
		
		
		
		
		
		
	
			
		
Hi
We are investigating performance issues with Aras Innovator using Dynatrace.
We found that GC Suspension was occurring when response times worsened.
However, as we continued our investigation, we found a strange situation in the distributed trace. SuspensionTime was shown to be longer than ResponseTime. I thought that SuspensionTime was included in ResponseTime and that SuspensionTime would be shorter than ResponseTime.
Does anyone know what situation would cause SuspensionTime to be longer than ResponseTime?
Regard.
Toshimasa Shirai.
Solved! Go to Solution.
03 Feb 2025 11:27 AM - edited 03 Feb 2025 11:31 AM
removed my answer, as I saw the information in the image was indicating my answer wasn't accurate... sorry for confusion.
03 Feb 2025 11:58 AM
Docs (https://docs.dynatrace.com/managed/shortlink/service-timing) defines Suspension time as: "The time during which any code execution is halted. It is usually caused by garbage collection.".
When you look into times of your requests, you can see that bottom 4 ran at almost same time, so probably Suspension time was calculated for all those requests that fell into same time bucket. Not sure how many requests are above upper one request.