I use version 1.3.4 normal, my clients complained about this problem and I went to test to see if it really existed, and I noticed the problem.Well if you're using the optimized version?
But in general thats just an overload issue which isn't really a bug.
Its like your PC when you're doing too much at the time it starts hanging
Can you tell me the differences from the optimized version to normal?
Still do not figure out the problemStill wanna know or are you already knowing it?
Does the optimized version only work for AMD or Intel as well?Ahh the optimized build is a by the compiler (gcc in my case) "optimized" build, to be precise with the flag -O3.
This means for example that, small functions will be inlined to improve performance.
There are some other opts. as well which result in a significant performance improve.
But as a disadvantage its harder for me to debug crash stuff, which was essentials in the early moths.
If 1.3.10-1 works out as expected and its fine I'll then switch the normal builds to optimized, because there are currently no known crashes which occur randomly, only on on snapshotrestore
Should be both?Does the optimized version only work for AMD or Intel as well?