Just add “–emulate-filter 256” option and let it work for a while to see if there is any issue.
With this option you’ll get exactly the same GPU and HDD load as after real plot filter reduction.
1 Like
There is no limit, but it probably doesn’t make sense to set it more than 256.
If you give me your address and the list of generated shares in that hour I can check if any of them are missing in our database.
Thanks that would help, I’ll send a DM. I’m mostly trying to determine if it is a client side or connection issue, which is my current suspicion due to there being no stale shares reported on the server side.
At this moment we have no plans for AMD support.
do you have plans to improve compression?
3 Likes
What about opencl support for intel dgpus?
like arc
We always try to improve it.
We’ll stick with CUDA for now, no plans for OpenCL.
yeah thats cool but what i meant is there new compression levels like c20 coming any soon?
No, there isn’t any.
Fair, rip. Also waiting on remote compute, it uses like 1-2MB/plot which adds up over the month to do over nfs.
However what we have works flawlessly
I see big drops in my hourly reward, time to time:
But I don’t see anything wrong in my logs, usage is low as expected and no delayed signing points :
:~$ docker logs nossdfarm | grep “were not processed”
:~$
How can I investigate this further or are these drops expected as it is part of the random variation?
Good for you, if it makes you feel good.
Does anyone know if there is a NOSSD discord?
I think their main support is on Telegram, don’t think I’ve seen a Discord channel mentioned.
1 Like
Ok, thanks for the info
I checked Telegram, there is nothing there. I only saw old announcements.