Writing Twice #18
Comments
StaticRip
commented
Jun 10, 2017
|
Did you happen to find a solution? I have the same problem with my 5TB drive it filled up to 4.4TB then the nonces dropped to 500/min and the % started going up too. Intel i7 3700 Restart for now? |
|
I experienced the same problem when I tested it during development. Back then, the plotting performances were so bad with this writing strategies that I nearly removed the whole feature. Based on what you say, it may be a multiple allocation with fragmentation issue. A solution would be to pre-allocate the output file to the final size. I'll try that as soon as possible. |
arihancc
commented
Jun 10, 2017
•
|
@StaticRip No, haven't found a solution yet other than 1) wait and let it do its thing 2) use xplotter instead. @bhamon Would it be possible to do it like xplotter does when run as admin? It makes the file the correct size instantly. Also if you would like me to test anything that might fix it just let me know! |
|
@arihancc Yes it would help me a lot, I can provide you a version with a quick fix for tests purposes. Which OS are you running? Which arch (x86, x64)? |
arihancc
commented
Jun 10, 2017
|
@bhamon Hey Windows 10 x64 :) |
|
@arihancc Can you test that pre-release? |
arihancc
commented
Jun 10, 2017
|
Hi just been trying it out. It seems to have the same issue. |
arihancc
commented
Jun 11, 2017
|
@bhamon Hey, Same issue. It allocated the file looking at the file size but still froze at 0.58% |
|
@arihancc At this stage, the fact it "frozes" is just because it is writing to disk the first N plots (N varies depending on the staggerSize you used). What is the content of your device.txt file and the command line you're using? |
arihancc
commented
Jun 11, 2017
•
|
My "Run script"
Devices.txt Using these it froze for roughly 32 minutes before the percentage started going up from 0.82%. |
|
@arihancc Can you try this version? You have to launch it with administrative rights to have a large writting speed enhancement (from an eternity to 1min per plots on my rather old computer). |
arihancc
commented
Jun 12, 2017
•
|
@bhamon Hey that seems to be working! Only thing is for windows (right click run as admin) the run script requires to look like this or you get that it cant find gpugenerator.
(just encase you wanted to add it to the docs, then you can simply right click run as admin the bat file.) Thanks so much for trying to figure out the issue! :) |
|
@arihancc Glad to hear it. Next step is to find a workaround for linux and OSX. I'll need some more beta testers. |
de-luxe
commented
Jun 12, 2017
|
@bhamon Quite sure you will find a lot of testers if you ask for it here: |
disrvptor
commented
Jun 12, 2017
•
|
Using this version just crashed on Windows 10 x64. Application Error (from Event Viewer)
Followed by the following Application Error
devices.txt: 1 0 1152 192 6144 Console
Update 1: It may have been a Windows issue with the RAID0 setup on that drive. Still verifying. |
|
@disrvptor Glad you've found the source of your problem. @arihancc Yes, it comes from the fact that running it as Administrator chnages your cwd. New version (4.1.0) is out. I'll provide Linux/MacOS binaries soon. Let me know if you find issues. |
danny91 commentedJun 3, 2017
Hey, not sure if this a bug or something i'm doing wrong.
When plotting (In direct mode) i have noticed it will freeze at 0.??% and it will stay at that percentage until it has filled all the space on the drives you have plotting. Once it has filled them it then starts again from the beginning and actually starts plotting. This i'm guessing roughly doubles the time. Only on the second pass does the percent start going up. The free space on the drives does not decrease anymore at this point.
Example mine was stuck on 0.7% for roughly 12 hours on 2 3TB and 1 2TB drives. After 12 hours it had wrote 3 plot files (one to each the correct size) then it started again and the percent started increasing.
During the "First" pass the GPU remains at 0% load and on the second round it is actually used.
During the second round no Reads are done from the drives (from what i can tell from watching it) Meaning its not trying to optimise what it wrote the first time.
Any input / help would be appreciated!
Thanks
Intel i7 4790K
16GB Ram
GTX 970