Jump to content

etherbattx

Members
  • Posts

    627
  • Joined

  • Last visited

Everything posted by etherbattx

  1. does vulkan use MSAA?
  2. forgot to mention, yes threads can be programmatically set to a particular CPU core, but they shouldn't do that. it can really mess things up. even microsoft recommends against doing it. microsoft says, "Thread affinity forces a thread to run on a specific subset of processors. Setting thread affinity should generally be avoided, because it can interfere with the scheduler's ability to schedule threads effectively across processors. This can decrease the performance gains produced by parallel processing." i'd be very surprised if DCS took this route.
  3. i don’t think we need to worry about thread bouncing. modern operating systems will bounce a thread between cores “on purpose” to spread the heat load and keep the chip cooler. this enables faster clock rates and more time in the boost modes. there is no performance impact to “bouncing threads” so this is a good thing to do. this is one of the reasons we caution users from playing around with core affinities. in most cases the operating system knows “way more” about the intricacies of the hardware than the user does and it is able to make better choices in how to utilize the compute resources.
  4. New Sticky Suggestion To Improve VR Performance i'm not sure that was ever correct. if it was it was a long, long time ago. windows programs have been multi-threaded by default for the last 15 years. even if the developer does not create additional threads themselves, windows will. open task manager in windows vista or later version of the OS and you can see for yourself. and unless you take action to prevent it, those threads will run on any available core (that is not already busy executing another thread). when i checked last week, DCS was using 13 threads, 3 of them being used heavily. when those threads are ready to do work, they are assigned to a core for execution. although you can use a utility to force those threads to go one at time and take turns on a single core, windows will not schedule them that way. windows will, be design, try to spread those threads out across multiple cores (i.e. more than 2!) as best it can.
  5. New Sticky Suggestion To Improve VR Performance do you have any utilities, like process lasso, installed? something you installed way back and forgot about? maybe one of them is configured to change the DCS core affinity settings.
  6. Samsung EVO SSD's and Rapid Mode. how does this work, technically? is the drive so fast it can read stored data faster than the computer can handle, so it buffers the extra data in ram until the computer is ready?
  7. yes. current builds use at least 3 threads which your operating system will assign to any free cores for execution. your 4 core machine will work great.
  8. CPU Bottlenecking? hmm... not sure i follow what you’re saying you’re saying that DCS had code to limit the number of cores used, and this has now been adjusted (fixed) to allow additional cores? on the release branch, it’s been using all the cores ever since i first checked (about a year ago).
  9. GPU or CPU? that’s technically correct, but generally the differences are small enough that they can be ignored. as for AMD, we have been keeping our fingers crossed for 12 years or more. god willing, this time it will be different. if ryzen provides better performance in real life (not synthetic tests), I’ll happily switch.
  10. i’ve tested in single player and multiplayer with monitor and with VR, and DCS always uses multiple threads and more than 2 cores. 4 cores seems to be the sweet spot, but the details don’t really matter, since all modern cpu’s have at least 4 cores.
  11. Only two cores. 1-core for audio 1-core for everything else i don't think that's correct. and you can't really think of "cores" when it comes to an executing process. it's more about the "threads". in modern operating systems, an application creates and uses a thread for it's execution. some apps create one, some create 200+.. but in either case, the "thread" is the unit of execution. the "core" is just a compute resource where the thread executes or "runs". if you launch DCS and let it go for a while and look at the threads (units of work, which get assigned to 'run' on a core), you will see that there is around 50 different threads for the DCS process. if you examine the total execution time for each thread, you will see that while most are idle, some do real work. in my multiplayer caracas test case: 34 threads didn't do much at all (almost no execution time) 13 threads "ran" for more than 1% of the total DCS process execution time 3 threads consumed more than 73% of the process execution time (38%, 23% 12% each) given the data, we can see that DCS used 13 threads (out of 50) to do the work of the sim, and 3 of those threads were doing the bulk of the work. it doesn't make sense that one core does "audio", and one does "everything else". there is a lot more going on than that. in any case, those threads will be assigned to a physical "core" when they are "ready" to run. if you only have a single core machine, all those threads will be assigned to that single core and be forced to run serially, one after the other. but if you let windows do it's job, it will assign as many "ready" threads to run as it can, onto any of the available free cores. so, those 3 main threads do a lot of work. and the 10 other active threads do work too (but less). and that means there are 13 threads that will be scheduled onto cpu cores every time they are "ready" to run. so rather than saying DCS "only uses 2 cores, 1 for audio and 1 for everything else", i would say DCS uses 3 'main' threads heavily and 10 quite a bit less often. and for sure you don't want 13 threads running on a 2-core Core-Duo chip. DCS is not just a 2 core sim, it's definitely more.
  12. i wasn't aware of that. i searched around but haven't found any more information on this issue. do you have links? what about the 9700K? and Z390 board? are they affected? i'm not seeing that behavior. dcs is using all cores.
  13. and sometimes on sale for $49 USD. can’t go wrong at that price.
  14. very true, but never underestimate the power of marketing and hype. millions of $$$ have been made using those simple techniques.
  15. Windows will use all cores by default. you shouldn’t have to change this,unless it was previously set to something else and constrained, either manually or using a utility like process laso or something else.
  16. agreed. and i don’t mind paying more for the Mercedes, i just wish the Mercedes alternatives worked as well as the Ford.
  17. nice. i want a new card, a faster card, but i’m not paying for RT silicon i can’t use.
  18. ok. then please explain to silentbob1 what happened with his upgrade.
  19. GPU or CPU? * 3.6Ghz is 3.6Ghz, no matter the CPU, unless this is faster than your old one, zero impact on FPS * 32GB ram - unless it’s significantly faster speed than your old ram, zero impact on FPS * new motherboard? - zero impact on FPS * SSD’s have zero impact on FPS
  20. RTX 2080Ti or AMD Radeon vii inventory is moving slowly and their stock price is way down... there is not very many ways to spin the bad news. something is not working very well.
  21. as we’ve seen over and over, paper specs are one thing, real life is another. personally, i prefer a unit that works better in real life.
  22. the problem is, finding something for the other 6 cores to do. any spare apps?
  23. stocks down! marketing to the rescue!
  24. RTX 2080Ti or AMD Radeon vii they could have a change of heart like they did with 3D once they realize nobody is using RT. they have done it before. as a manufacturer, they can push and encourage a direction, but if nobody is going along they will have to rethink and reset.
  25. i’m still holding my breath for a fast non-RT nvidia card. a card like that would sell like apples. everyone would have one.
×
×
  • Create New...