I've been running BF4 for a few days on my new PC and it runs great most of the time. Single payer runs from 70-110 FP on high settings but periodically slows down to 30-50 when something needs to load. On multiplayer, however, it runs smoothly for a while and then chugs all the way down to 20 or below.
I opened up task manager in windows and the frame rate chugs seem to coincide with the disk performance peaking and staying pegged at the top. I'm not sure why. Could this be fixed with turning hyper threading off?
My PC is running an Intel 3570K, MSI GTX 760 HAWK, 4 gigs 1600 RAM, and a WD Caviar Blue 1TB HD. All items running at stock clocks.
Didn't know that, thank you! I'm still getting back in the PC game, so learning all the new tech is a bit of a process. I just saw the fix in another thread reference hyper-threading.
What is your RAM usage at during these dips? Since the minimum requirement is 4gb RAM for BF4, it could be that the system is using the page file quite a bit, which could impact performance.
I never saw RAM go past 85% usage during gameplay. It would usually hover around that mark and occasionally drop a hair lower. I thought the low RAM could be the issue as well until I saw the system usage in task manager. Just to be clear, it does seem like the machine is using the page file often since my disk pegs at 100% and hangs there. My understanding is that this is symptomatic of the system using the page file frequently. Would disabling the page file be advisable as in this thread: http://www.tomshardware.com/forum/id-1658680/prevent-10... or would it be better to set a fixed page file size?
Martell1977 seemed to have been on the right track. I did some digging into page file usage on Windows 8.1 and found other people had this issue. I guess the system goes screwy when you are running a memory intensive program. Don't know all the details or technical aspects, but the fix seems to have been to set a manual page file size. It fixed it in my BF4 preliminary testing, at least. Time will tell if it legitimately fixed it, or if I just got lucky.