Closed UselessGuru closed 6 years ago
Hi @UselessGuru
Not sure if you're still looking for this info or what info you require, but here we go.
Ran a test on my 13x 1070 Ti rig now with these new .ps files and Excavator 1.4.1a Cuda 9.1 and 390.65 nvidia drivers:
@UselessGuru Would love to hear your advice on how to find out why EN2 keeps crashing for so many algos.
@evanvz
Thank you for the logs. But what I would like to know cannot be logged :-(
I have edited the test instructions to clarify the things to watch.
Hi @UselessGuru
Noted.
Seems @Braintelligence it a betetr job.
Just trying to give my 2c helping you with your great program.
Cheers.
@evanvz I'm sorry, I don't understand what you wrote when you referred to me ☹️. What I wrote sadly won't help @UselessGuru at all, because I don't have AMD cards on that rig.
I hope that my observations can help others and maybe @UselessGuru might drop a hint on what I could try to optimize my rig and make EN2 work, since it looks promising for Equihash.
@Braintelligence
Would love to hear your advice on how to find out why EN2 keeps crashing for so many algos.
EN2 is running two treads per miner = double the amount of ram needed. This works for some algorithms, but not for others.
make EN2 work, since it looks promising for Equihash
No chance. Excavator does not have enough memory on the graphics card (happens for me too)
@UselessGuru Are we talking VRAM (I mean: memory on GPU) or RAM (system memory on the mainboard)?
@UselessGuru Can do some testing for you on Friday.
Are we talking VRAM (I mean: memory on GPU)
VRAM assume (I have 32GB of RAM in my box, 3 GPUs and are still getting the same errors)
@UselessGuru I see, thanks for clarifying! So it could work on GTX 1080Ti with their 11GB VRAM?
So it could work on GTX 1080Ti with their 11GB VRAM?
Nope, some algogorithm use a percentage of available vram. If they take more than 50% then 2x 50% -> bang!
@UselessGuru Makes sense, so this only works for some algorithms I guess. Crap. 😸
Tested 1.4.1a earlier with no crashes on my 3x1070ti,3x1080,1x1070 rig.
1.4.2a insta crashes. Will test more
added the direct path in the miner file for mpm to download and 1.4.2a is benchmarking now
added the direct path in the miner file for mpm to download and 1.4.2a is benchmarking now
You are supposed to do a manual DL and install. ;-) Due to EULA restrictions we are not allowed to support automatic DL.
I tried the manual way. Must have fat fingers, couldnt get it to run.
Am at a lost as to why only 2 out of 3 gpus are being used. Excavator picks up all 3 cards when initialising
Please post the command line & json file
Got this from the excavator dev:
Ok, I see what's the problem. Wrong device ids in worker.add methods.
This
"method": "worker.add","params": ["0","1"] "method": "worker.add","params": ["0","2"] "method": "worker.add","params": ["0","3"] Should be:
"method": "worker.add","params": ["0","0"] "method": "worker.add","params": ["0","1"] "method": "worker.add","params": ["0","2"] Device ID of your first GPU is 0 not 1 and so on..
You're adding worker to a device with id 3 but that device doesn't exist, in the mean time your first GPU doesn't get a worker, that's the reason it's idle.
I will manually edit the json file and check
@geckah
Could you please post the output of the following command:
[OpenCl.Platform]::GetPlatformIDs() | ForEach-Object {[OpenCl.Device]::GetDeviceIDs($_, [OpenCl.DeviceType]::All)}
Also post an example of the created json files. Thank you.
Here is the json file NiceHash_Nist5_1_Nvidia.txt
I'm sorry, but how do i get to output that command?
I'm sorry, but how do i get to output that command?
getting an error with that command:
Unable to find type [OpenCl.Platform]. At line:1 char:1
+ CategoryInfo : InvalidOperation: (OpenCl.Platform:TypeName) [], RuntimeException
+ FullyQualifiedErrorId : TypeNotFound
OK, run pwsh from the MPM directory then type 'using module .\Include.psm1' and try again.
here you go somefile.txt
somefile.txt
Thank you - I think I see the problem. Your CPU is also a GPU. I have updated the miner files: ExcavatorMiners.zip Can you update and test - thank you!
Thank you - I think I see the problem. Your CPU is also a GPU. I have updated the miner files: ExcavatorMiners.zip Can you update and test - thank you!
Sorry for the late reply. Testing now, all cards are being utilised now. Will update on the results then move on to test rigs with more gpus
nist5 alexis78cuda9 208MH/s EN2 157.59MH/s EN1 154.27MH/s
neoscrypt EN1 3.55MH/s klaust 3.18MH/s EN2 fails to run, couldn't catch the error
lyra2v2 EN2 135MH/s EN1 132MH/s polytimos 131.95MH/s
blake2s polytimos 13.02gh/s EN1 12.52gh/s EN2 12.4gh/s
Testing now, all cards are being utilised now
Thank you. Good to hear!
EN2 fails to run, couldn't catch the error
That is somehow to be expected, some miners/algos eat up too much VRAM. Let MPM fail during benchmark, it will report 0 hash rate and will never try this miner/algo combination anymore.
Testusers wanted!
In an attempt to create AMD only and NVIDIA only miners I rewrote the Excavator miner files. This will fix https://github.com/MultiPoolMiner/MultiPoolMiner/issues/1075 Since I do not own AMD hardware I need some assistance.
How to do do this quick test:
You need to have a mixed rig with AMD and NVIDIA cards installed. Then
Manual Update of Excavator Version 1.4.4 alpha NVIDIA: https://github.com/nicehash/excavator/releases/tag/v1.4.4a
You have to update manually, because Excavator is a proprietary software by NiceHash and has a special EULA.
Unfortunately I cannot verify this behavior from the content in the log files - so uploading logs won't help me :-(