Ploting with two NVIDIA Quadros M6000 using Direct mode.
-
@nixxda Oh I see. Thanks man.
BTW...
Do know if there's anyway to use my GPU memory for Plotting?
-
@Wolf do you mean adjusting "devices.txt" to your GPU's?
I had to do that by "try and error"!-/
-
ahh, found it again!
there's an an older description for GPU plotting https://docs.google.com/document/d/1mTwPqBbkjfL3abIPkqNRcHpQp-3r2de7sDdmANJpR3Y/edit?usp=sharing found here https://bitcointalk.org/index.php?topic=731923.0But other parameters work to! sometimes!-)
-
one more.... you'r allready using the GPU memory for creating the nonces and your 24Gb RAM as an "write buffer" so to speak!
-
@nixxda yes for some reason its not wanting to use my gpu memory. I have this configuration
0 0 1024 128 900
0 1 1024 128 900For the Global Work Size
globalWorkSize: The amount of nonces to process at the same time (determine the required amount of GPU memory). Should be a power of 2.Both of my Quadros have 24gb of memory if i set the over Global Work Size over 2048 it throw me this error... [ERROR][-36][CL_INVALID_COMMAND_QUEUE] Error in step2 kernel finish
-
@Wolf setting this up is a bit weird!
but doasn't the last Number have to be:
"hashesNumber: The number of hashes to compute per GPU calls. Must be between 1 and 8192. Use a value under 8192 only if you experience driver crashes or display freezes."
according to this page?I ended up with this
1 0 1024 256 8192
dont really know why but it works! so I dont touch it!
btw. "gpuPlotGenerator setup" did not work for me. Had to do it manualy be try and error.
-
wow nonces Speed :O
-
@nixxda said in I'm having trouble with GPU Plotting using Direct mode.:
Plotting in direct mode first creates the file and then writes sorted data into it
Ok so it finish creating the file and after that it going really really slow creating the data into it.
Im getting 116.35 nonces/minutes. Can someone please tell me what is going on?
-
@Wolf post screenshots of your devices.txt and the command used with gpuplot
-
@Wolf said in I'm having trouble with GPU Plotting using Direct mode.:
@nixxda said in I'm having trouble with GPU Plotting using Direct mode.:
Plotting in direct mode first creates the file and then writes sorted data into it
Ok so it finish creating the file and after that it going really really slow creating the data into it.
Im getting 116.35 nonces/minutes. Can someone please tell me what is going on?It will increas as it goes along, mine does the same thing, writes the file at 40-50K nonces per minute and once done it optimizes it which starts off at ~100-300 nonces /minute and goes up to about 4000
-
@Focus Will it be faster to GPU Plot first and then optimize after?
-
@iKnow0 Here is my devices.txt configuration
0 0 2048 128 2048
0 1 2048 128 2048
-
@Wolf said in I'm having trouble with GPU Plotting using Direct mode.:
@Focus Will it be faster to GPU Plot first and then optimize after?
Just do it the way you are and be patient, I tried optimizing after with so-so results
-
@Wolf Uhm... 23GB GPU memory, oh my god :)... Maybe experiment mad things like increasing 3rd number:
0 0 65536 32768 600 (16GB of memory here)
If it works, increase the last value. I don't know if it works, but maybe this is the way...
-
@Dario's-wallet I have made a post about the GPU Plotter not using all of my gpu memory and the differance between increasing the third number here..
https://forums.burst-team.us/topic/2656/gpu-plotter-is-not-using-my-gpu-memory/2
but I see that you increase the 4th number too I haven't did that one. Also 65536 suppose to be 64GB right?
-
@Wolf 65536 it's the memory space measured in number of nonces: 65536*256KB(size of one nonce)=16GB
In my post I mean set the 2nd number at 65536 WHILE you set the 3rd at 65536/2=32768 ( a lot of parallel threads), then increase the last number starting from 600 (typically 600 is a low value)...
-
@Dario's-wallet said in I'm having trouble with GPU Plotting using Direct mode.:
@Wolf 65536 it's the memory space measured in number of nonces: 65536*256KB(size of one nonce)=16GB
In my post I mean set the 2nd number at 65536 WHILE you set the 3rd at 65536/2=32768 ( a lot of parallel threads), then increase the last number starting from 600 (typically 600 is a low value)...Dario, what do you suggest on a system that has a RX480 and 256GB of ram ?
-
@Focus Hi mate, I'm so sorry for late reply :(, when I wrote my last post was 3 am and I fell asleep...
However for me is better always start with default values, then tweak. Every system can be a bit different. A good value for global work size could be 32768 (8GB RX480 version, without screen output). For the last two values is more difficult to say... Maybe a solution could be set the hash number at a middle-high value (like ~5000), find the higher local work size that works, and then increase the last number...
However a card like the RX480 I think can top every hdds write speed: if you have to plot more than one hard drive (@AdamGuerbuez system?:)), I suggest you to parallelize plotting (two drives at same time, maybe more, you have to try...)
-
@Dario's-wallet with that said.. Do you know a good stagger size for a 10TB Harddrive? Because every time that I increase the global work size(the third number in the device.txt file) for some reason I have to decrease the stagger size.
gpuPlotGenerator generate direct D://3225037558013223906_0_38075392_105472
pause"Updated"
I'm unable to go with this configuration0 0 65536 32768 600
0 1 65536 32768 600Here is the error for this configuration. Even if I divide it by 2 all the way till the third number is 4096...
[ERROR][-54][CL_INVALID_WORK_GROUP_SIZE] Error in step1 kernel launch
-
@Wolf No probs for the stagger, 105472 is ok, in direct mode the output file will be 3225037558013223906_0_38075392_38075392
About the devices configurations...mmm...maybe try lowering the local work size number increasing the hashes per call (6200 is just an example, maybe also try with 8192):
0 0 65536 32768 6200
0 0 65536 16384 6200
0 0 65536 8192 6200
And so on...




