I’d love to hear an official statement about the bump, but the fact of the matter is, there isn’t even any doc available that mention the current practical limit of 8 on Windows / skepticism does play an important role, but upending someones interests based on the ‘anecdotal evidence’ is silly. So I guess that’s why neither NV nor AMD are hard pressed to solve this. You can use Linux where you don’t have this limitation, and the mainstream mining utils do have Linux ports. Like within the 5% margin, and it’s a one time cost. The savings are minuscule when you increase the number of GPUs/system. Most cases don’t support more than 8 GPUs anyway. You can have up to 2x8 GPUs if you mix vendors, which is sometimes even desired when you do multi-algo/multi-currency mining. Etc.īut this problem affects really few people, because And ATX boards installed in rack mount chassis, sometimes with 2 ATX PSUs installed. That’s why you have GPUs connected to the boards via x1 connectors. But miners are really good at working things around. I was to say it’s also way too high, but then I realized now they sell mining boards with up to 19(!) GPUs supported.Īnyways, you’re right that NV and AMD should definitely fix this, and/or push MS to allow a fix to happen.
That’s the way it is.Ībout this I’m also sceptical, 50 seems indeed too random, because it’s not a power of 2. Like a file on NTFS can be 16TB at max, and a filename can be 255 characters tops. Mostly because there’s no such thing as “infinite”, you have to set limits and boundaries which seem reasonable at the time.
Here’s the deal: in the world of computing you always have “arbitrary” limitations. The fact that this has not happened would seem to indicate it is more than an (arbitrary) driver limit. My take: Given the popularity of mining Ether, if the issue were purely a driver issue, I think both AMD and NVIDIA would have been falling all over themselves to get a fix out quickly so they can sell more GPUs to miners before their competitor does. An OS switch cannot be a serious obstacle to a dedicated miner, I would think. So keep trying new Windows driver versions or try switching to Linux if tired of waiting. One counter example does not constitute a proof.īe that as it may, if the “associate to an AsRock employee” is correct (and you seem to think s/he is), all your worries will be a thing of the past soon. And contrary to your assertion, I see no proof that this is not an issue with BIOS resource limitations, such as memory aperture configuration, in some cases. Since the observed limit applies to both NVIDIA and AMD hardware, it is at least conceivable that this limit is imposed by WDDM 2.0 (the Windows 10 driver model).
0 kommentar(er)
