Poor performance on Linux
|
Hi!
On my PC (Xeon E3-1230v2, GTX1650 4GiB, 32 GiB memory) the fps can easily drop to 0.25-0.5 -- yes, 2-4 seconds between each frame. Usually, the next frame I see is that I've died again. This is not challenging, it's s*-#*!*@-. Wine is up-to-date (v5.9), and I use dxvk 1.21. All setting is on the lowest possible option, and I run the 64-bit executable with --noasync. Note that, at the beginning it runs smoothly for a while, but after 1-1.5 hours the fps gets a bit lower (barely noticable), then drops below 1 fps super fast with 3-7 monsters on screen. Resulting in exp loss, ofc, which is freakin' annoying. I think a GTX1650 should handle it, I believe something is broken in the game, because no other game produces this poor performance. The GTX1650 is brand new, I recently bought it to replace a GTX750, because I thought the low fps is because the old graphics card. Do you have any idea? Just to be precise, the game should be playable on "PC", which does not mean "Windowz", so Linux is also included in the "PC" term. Or the "PC" is misused. TIA Last bumped on Jun 1, 2020, 12:18:37 PM
|
|
" When you look at game requirements, under the OS (which stands for Operating System) do you see any game where it stands written - PC - ? Not to mention that Windows, just like any Linux branch, is not a PC, it's the operating system that runs said PC. I thought someone using linux would understand the difference, a regular windows user might not but...damn... Now for PoE, the supported operating systems are Windows XP SP3/Windows 7 SP1/Windows 8/Windows 10 Any other OS be it Mac or Linux are not officially supported - thus experiencing any performance glitches within those environments is nonessential and unless can be narrowed down to an actual precise cause be it hardware or software related, is mute at best. TL/DR PC is not an OS, you ought to know the difference, linux is not officially supported, and in fact as far as gaming goes is an oversized emulator when it comes to games, so glitches errors and crashes are something you should be expecting. No rest for the wicked.
|
|
" Obviously, PC is not an OS, I know that, but this is not the most critical issue, I wrote it just to be clear (seems, it is not): PC means multiple OS, such as Linux and Win (an many other OS, as well), unlike the "xboxone" and "ps4", which do not have this variety. That was what I meant to say. That's why saying "for PC" is not that precise. Wine is not an emulator. It is a windows program loader. Huge difference. (The dxvk part is essential, without it the game does not run smoothly even after freshly starting the game. What is does? It compiles DX11 stuff to Vulkan.) Qemu on the other hand is an emulator (as well as DosBOX, as a fun fact). qemu-kvm is a virtual machine with native CPU support, therefore it is not an emulator neither. I tried it on win7 in a vmware, the performance was poor in it too. |
|
|
The fact still remains that outside of supported operating systems, you cannot expect a good performance, or even be able to run the thing.
But as for your issue, it really does sound like caching issue, it could also be a memory leak within the game engine but it's unlikely since those things affect 100% of players, no exceptions. Those are the only two things that come to mind if we are talking overtime degradation of performance. Check if within your nvidia control panel the shader cache is enabled, if it's not turn it on, if it is, nuke it - see if that helps, since it's linux we are talking about, i have little to no idea how caching is handled within that thing. No rest for the wicked.
|
|
" I would argue a bit about the OS topic, because technically it is the same hardware, and the program is also the same. It is not so uncommon though, the same program can behave differently on different environments. This considered also another test scenario, and I do this. Sometimes it can reveal nasty stuff. No offence, but this is a bit more sophisticated in case of software systems than "it's unlikely since those things affect 100% of players, no exceptions". You can never know, it you don't have the right test case, and assuming something is a very, very bad idea. :) On the other hand, the "supported" topic is a bit subjective. If you look at the "PC" term, you might expect to run on a PC. Okay, the cache was a good call. It took me a while to build a faster test method, then just waiting. I had to test different configurations. The nvidia setting was there, the cache option was enabled, so I disabled it. Nothing changed, or, at least, it was unnoticeable. It turned out, the game itself has a shader cache, which is the "ShaderCacheVulkan" in the game's directory. I could not set the game to ignore the shader cache, so I did it the hard way: cleared that directory, and removed all permissions from it. It worked, the cache was not used anymore. The game performed a bit better after this, but at some point, the huge fps drop kicked in again. I would say, the recovery from this situation was a little bit faster, but this might be a placebo effect only. I even tried without the dxvk, since the renderer is Vulkan. I would say it was a bit better, but nothing significant. In summary, disabling the cache helped in some sort, the smooth operation was a bit longer, but the performance degradation was inevitable. |
|
