Slow cpu

#1 Hello guys. I recently bought a whole new system, and I have a question: is it normal that a Ryzen 3700X not being able to handle 900p@60 x264 slow preset?When I try to stream in 720p@60 x264 slow preset, it goes fine, no frame skippings. But when I try 1600x900 or 1920x1080, I get many skipped frames message in the Stats window, the "Skipped frames due to encoding lag", but CPU usage is not reaching not even 30% usage, according to the OBS Stats window. Very strange.I have a very capable M.2 SSD (signature for full PC specs), so I don't think it's the issue. I tried to record locally, same thing happens.In summary:720p@60 x264 slow preset = fine900p@60 x264 slow preset = skipped frames due to encoding lag1080p@60 x264 slow preset = skipped frames due to encoding lag1080p@60 x264 medium preset = fineNone of the above configuration reach 30% CPU usage.Is it a CPU limitation? Twitch limitation? Or OBS limitation? 2019-12-17 19-21-02.txt 31.6 KB · Views: 187 #2 Most likely a limit of how many threads FFMpeg can utilize for encoding. Your CPU has plenty of threads left over, but there's only so many that can be practically used for encoding. So the CPU utilization graph is not a complete metric for figuring out how slow a preset a CPU can use. #3 What you're seeing is correct for your CPU. I would not trust the OBS cpu usage report -- you'll find a much more telling view using Task Manager's performance tab.The 3700x cannot realistically do slow on anything above 720p60. You would need to jump up to the 3900x if you want that, and even then you'll encounter the occasional bit of encoding lag, even though it doesn't ever go above 70%.EposVox has a really good set of comparison videos specifically talking about the Ryzen 3000 series encoding capabilities for OBS, if you want to look those up. #4 Thanks for the responses, guys.I kinda managed it to stream at 1080p@60 slow preset by adding the x264 option "threads=16". But it has peaks of 80% CPU

CPU processing power your computer is currently using and has been using over time. The Memory and Physical Memory Usage History boxes display the amount of memory that is being used and how much has been used over time. As you can imagine, this information is very useful in determining why your computer may be running slow. For example, if you find your computer is slow and find that the CPU utilization is at 100%, then you know the slow down could be caused by a process using up to much CPU power. You can then go to the Processes tab to see which process may be using up all the CPU power and close it. If you find that there is no particular CPU causing a problem, then this just may be a indication that it is time to upgrade your CPU. The same diagnostics can be used with memory. Many people do not realize that memory is a vital component of fast computer. If your applications are using up all of your memory than Windows will start writing pieces of memory to a file a on your disk drive. This process is called paging and when it occurs your computer slows down significantly. By using the Performance and Processes tab of the Task Manager, you can quickly determine if a lack of memory is causing your computer to perform more slowly. Networking Tab The Networking tab allows you to have a general idea of how much traffic is flowing over a particular network interface on your computer. At the bottom of this screen you will see a list of all the network interfaces on your computer. Above that you will see graphs for each interface that show the network traffic flowing over them. The Networking Tab This information can be useful if you are wondering why your Internet or network connection may be to slow. For example, if you see that your network interface is at 100% utilization then something in Windows is using up all of the available bandwidth. You can then determine what program is using

Within few CPU instructions. SQL Server tasks acquire spinlocks by doing interlocked CPU operations in a tight loop, so contention on spinlocks burns a lot of CPU time (CPU usage counters show 90-100% usage, but progress is slow). Further analysis need to be done using sys.dm_os_spinlock_stats:select * from sys.dm_os_spinlock_stats order by spins desc;For further details I recommend reading the Diagnosing and Resolving Spinlock Contention on SQL Server white paper.RESOURCE_SEMAPHORE_QUERY_COMPILEThis wait type indicate that a task is waiting to compile its request. High wait times of this type indicate that query compilation is a bottleneck. For more details I recommend reading Troubleshooting Plan Cache Issues.SQLCLR_QUANTUM_PUNISHMENTThis wait type occurs if you run CLR code inside the SQL Server engine and your CLR code does not yield the CPU in time. This results in an throttling of the CLR code (“punishment”). If you have CLR code that can potentially hijack the CPU for a long time you must call Thread.BeginThreadAffinity(). For more details I recommend watching Data, Faster: Microsoft SQL Server Performance Techniques with SQLCLR.Special wait typesTRACEWRITEThis wait type indicate that tasks are being blocked by SQL Profiler. This wait type occurs only if you have SQL Profiler attached to the server. This wait typeoccur often during investigation if you had set up a SQL Profiler trace that is too aggressive (gets too many events).PREEMPTIVE_OS_WRITEFILEGATHERThis wait type occurs, among other things, when auto-growth of files is triggered. Auto-growth occurs when a insufficiently sized file is grown by SQL Server and is a hugely expensive event. During growth event all activity on the database is frozen. Data file growth can be made fast by enabling instant file growth, see Database File Initialization. But log growth cannot benefit from instant file initialization so log growth is always slow, sometimes very slow. Log Auto-Growth events can