Jump to content

etherbattx

Members
  • Posts

    627
  • Joined

  • Last visited

Everything posted by etherbattx

  1. we are not "in the dark". if you use a process diagnostics tool, you can see that DCS uses many threads (execution contexts), and the way operating systems work, the operating system will schedule those threads to an available cpu core when they are ready to run. if two (or more) one of them are ready to run at a given time, the operating system will schedule each thread onto a separate cpu core where they can run simultaneously and make use of multiple cores. if you feel like it, you can constrain your system and limit what cpu cores you allow DCS to use, either manually or by using a tool like Process Lasso. some users claim DCS runs faster when you constrain it, but i haven't seen that (and it doesn't make much sense that it would)
  2. so, what you're saying is, we can limit DCS to two physical cpu cores (tell Windows not to distribute threads across multiple cores), and it will run correctly with no performance loss?
  3. this is not correct. it maybe have been like that 5 years ago, but it's not that way today. if you use a process diagnostic tool, you will see there are many execution threads and more than two of them get significant execution time. if you want to test this theory yourself, set your cpu affinity to only 2 cpu cores and see how DCS runs. you'll know right away if it only needs 2 cores :)
  4. Best SSD to use for Dcs i have benchmarked my system. if you copy a lot of large files around between drives, it’s noticeable. but booting windows isn’t much (any?) faster. for loading games, in a blind test, you’d be hard pressed to see the difference.
  5. Ryzen or Intel mid-range CPU are you sure this is what people are looking for? most of the thread posts in these forums are about finding and achieving the best performance. for apps like DCS, it really is about 0-60 performance.
  6. double the cores , double the threads double the performance. smh it’s like free magic all rolled up into one.
  7. i hope so, but right now the large game development companies are pulling funding away from VR, claiming the market is to small and adoption to slow.
  8. i like your analogy. the issue is that most software sees no performance increase from the preloading. even intel own material claims a maximum of 20%, and you can bet they benchmarked that with the optimum use case!
  9. 500% increase in fps from adding RAM? what happens if you add another 16GB ?
  10. with HT, if two threads get assigned to the same physical core, they have to share the single cpu execution unit. that's why you only see a 20% increase with HT (optimum case) instead of 200% sharing mean means coordination overhead and one waiting for the other to finish. that's why you don't get 100% utilization.
  11. 91% RAM, should i upgrade? how are you measuring that? windows will take advantage of available ram and use it for temporary storage. even if it’s not needed by an application (like dcs). to measure dcs ram usage, take a look at the “working set” size. that’s the amount of ram the process is actually using while it’s “working”
  12. Intel or AMD i was trying to help you understand that DCS is multithreaded and always has been. you said we were wrong and wanted to double down and argue. i am happy to have this conversation with you in private, but i would ask that you stop spreading the “dcs doesn’t multithreaded” misinformation in the forums. please reread what we posted. Hyperthreading is NOT a trademark name for multithreading. it’s a hardware feature that allows some workloads (almost never games) go a little faster in very specialized scenarios. it has very little to do with multithreaded applications and for most discussions it can basically be ignored altogether.
  13. The CPU doesn't "have" a thread, the number simply states how many it can process quasi simultaneously. i don’t think we are going to be able to help this guy. he’s a youtube/wikipedia expert telling developers how the OS and cpu work.
  14. those numbers look correct. rift cv1 is 90hz refresh ->. 11.1ms rift s is 80hz refresh ->. 12.5ms you can’t change that. it’s part of the headset design
  15. Intel or AMD yes mostly likely. and it would interesting to see the amount of difference in the real world. people sometimes think 2 hyperthreads = twice the performance but since the cpu execution unit is shared and only able to process one thread at a time, the results are not even close to 2x even intel’s own technical literature makes multiple references to “up to” 20% increase. and most likely they are testing with optimized workloads to enhance the increase. for most users with desktop pc’s HT’jng can be ignored, other than being able to brag about how many threads they have! :)
  16. can’t you also turn down the settings to reduce the details and textures?
  17. yes, exactly. it's a hardware construct and enabled/disabled in the BIOS HT's can not be created, adjusted, tweaked or targeted by a software program. to DCS, they are completely invisible. when one of the DCS threads is ready to run, the operation system may schedule/assign it to any of the cpu cores (real or virtual) to execute. the only way you can 'adjust' or control this is through the cpu affinity setting (process lasso, manual adjustment in task manager, etc)
  18. i think you are confusing terms. multithreading and hyperthreading are two completely different things. multithreading/multithreaded - a SOFTWARE construct where you break the execution task into separate threads. you create multiple threads with the CreateThread() API in the windows operations system. multithreading has been supported in Windows NT since 1993 and in Windows 95 since 1995, 12 years before Intel released the first dual core cpu. a program is considered to be 'multithreaded' if it calls CreateThread() more than once and has more than 1 thread in the process. hyperthreads - is completely different. it is a HARDWARE construct, where some of the fetch, decode work can be done by the core in parallel. windows supports this by treating the extra pipeline as a VIRTUAL core, to simplify the scheduling of tasks. you can NOT create hyperthreads in your program and you can't target them in your algorithms. the setting to enable hyperthreads is in the BIOS, not the software program. it's done in HARDWARE and managed by windows. when designing and writing software, HT can be ignored. there is nothing DCS or any other program can do do with or without a hyperthread.
  19. i agree with this. but again, you can see that yourself by looking at the thread count when Premiere is running ( i can send you a screen shot from my system you like)
  20. with regards to hyperthreading (HT). how does one create a program to use hyperthreads? there js no api in windows to do this
  21. Intel or AMD they might, but it’s not guaranteed. multithreaded programs have more than one thread and can use any number of cpu cores. there is no magic to it. you can use cpu affinity to test this yourself. just set a multithreaded process to use a single core. the process still runs. edit: maybe the following will help do you remember Windows 95? it supported muiltithreading programs (processes with more than 1 thread) back in 1995... yet, there were no multi-core cpu's to run it on until 2005, about 10 years later. multi-processing (more than one cpu) is not a requirement for multithreading or multithreaded execution. the only requirement for "multithreading" is for there to be more than one thread in the process.
  22. i forgot to ask. if DCS is not multithreaded, then why does it have more than 1 thread in the process?
  23. YES! this is exactly what DCS is doing. please, please open your favorite "process info" tool and see if the DCS process has more than one thread. (it does) then look at the cpu usage of each of those threads. are those threads using cpu time? (yes) think of this scenario - DCS can render graphics AND play at sound concurrently, at the same time on two different threads. this is literally the definition of a "multithreaded" application. i don't know how to explain this more clearly
  24. unless explicitly limited by the program or user (cpu affinity), any thread, in any process, can be scheduled to run on any available core. that is the main purpose of an operating system, to manage limited resources between various programs (in this case limited cpu resources). if it didn't do this, you could not run hundreds of software programs (with their thousands of threads) on a 4-core cpu. there would be too many threads for the limited number of cpu's and only a few programs would work at a time.
  25. Intel or AMD open a process tool and look at the “threads” section. you can easily see that there are at least 40 threads in the process. next, take a look at how much cpu time is used by each thread. you will see that every thread has some cpu usage, so multiple threads in the process and they are each using cpu time dcs is multithreaded. if it wasn’t, you could lock it to a single (1) core and get the same or better performance.
×
×
  • Create New...