![]() ![]() Ran it again today the same way and only getting 60 FPS at Resort again. What's annoying is I ran the Lasso for the first time yesterday and instantly saw an improvement and jumping up to and over 100 FPS. The low CPU usage is a GPU bottleneck (?) but that's fine for 1440p for me as I have Gsync.Ħ0 FPS is not at all acceptable and really makes you slip shots. Either people lie through their teeth or I have an issue elsewhere but I had the same issue with my 10k and this is a whole new mobo, RAM and CPU. I've followed the rules for NCP for Tarkov - texture filtering to high performance, vsync off, power management max, allow LOD bias etc etc.įirst off I feel like my 2070 S is a pretty woeful card vs what everyone is getting with it not just in Tarkov but in other games too at times. Process Lasso on always affinity - though I notice current shows all cores and has to be reticked no idea why. Latest drivers, Windows 10, blah blah blah.ġ440p, almost all low settings. Dell S2716DG 1440p 144hz and Gsync enabled.16GB DDR4 3200hz (XMP enabled, 1600hz dual confirmed in CPU-Z).RTX 2070 Super, 1440p - running around 95%. ![]() Moderator decisions are final, please respect the moderator team and their actions. Make sure to follow the guidelines outlined in the Reddiquette for a more pleasant experience. Recent News Official LinksĪs well as the above rules, the Reddit Content Policy is in place as well - please familiarize yourself with this. Please make sure to follow the rules noted below in the side bar. This is an unofficial, community-run subreddit. (or doing other things).Escape from Tarkov is a hardcore and realistic online first-person action RPG/Simulator with MMO features and a story-driven walkthrough currently in development by Battlestate Games. Then you can use this utility as a basis for implementing various policies for renicing executables. You can of course save the Perl code to a file, say onexecuting, prepend a first line #!/usr/bin/env perl, make the file executable, put it on your $PATH, and from then on use onexecuting /bin/ls renice. here is a crude implementation in Perl using Linux::Inotify2 (which, on Ubuntu, is provided by the liblinux-inotify2-perl package): perl -MLinux::Inotify2 -e ' Unfortunately, this won't tell you which process caused the event to trigger, but you can then check which /proc/*/exe are a symlink to the executable file in question and renice the process id in question.Į.g. Executing it will trigger an I_OPEN and an I_ACCESS event. If the processes in question are started by executing an executable file with a known path, you can use the inotify mechanism to watch for events on that file. Of course, the linux scheduler does a fairly good job at handling CPU bound threads by downgrading their priority and rewarding (upgrading) the priority of I/O bound threads - so even in high loads a script should be responsive I guess. notification events/hooks, which may have to be processed many more times per second. Lastly, considering the HIGH frequency of process changes, it may be better to handle all changes at once (polling at interval) vs. The overhead for that many different hooks might be much greater than simple polling. I don't think any OS is going to natively inform you of any change to any process metric. ![]() Kernel mode hooks are available for certain process related events in Windows (creation and destruction), but they not only aren't exposed at user mode, but also aren't helpful at monitoring other process metrics. I had a similar choice to make and have a hybrid solution in place. I develop a similar 'process and process priority optimization automation' tool for Windows called Process Lasso (not an advertisement, its free). Ironically, the more perfect solution may be the less efficient one in some cases. This is the real world though and sometimes compromises must be made. This is classic programmer 'perfection' thinking. That said, when hooks or notification events are available, or can be easily injected, they should certainly be used if the situation calls. If the polling overhead is low-enough, it far exceeds the added complexity, cost, and RISK of developing your own style kernel hooks to get notified of the changes you need. Sometimes polling is a necessity, and even more optimal in the end - believe it or not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |