Read Times
-
I'm not sure how to configure how it is utilized, since it is pretty much automatic with the miner if i'm not mistaken.
-
@VerdommeMan But yeah, I noticed that too.
-
@Jay.f the screenshot shows ,
1 Core ( Are you using a VM to mine? )
You should be using the AVX miner, fasterHave you tried a re-boot to see if it fixes the issue?
-
I'll create another thread for this. I guess it's a cpu issue. Plus, as you can see the 1 core isn't that bad, it's just the how it is utilized.
-
@Jay.f why do that? did you try the above to see if anything changed?
-
@iKnow0 Jesus, quick update. I launched the AVX miner... 62.8 Mb/s (First read only). No I am not using a VM to mine; I've rebooted multiple times, the issue stays constant. Though let's see how this AVX miner turns out.
-
@Jay.f if its only seeing one core, power down your PC, open it and check to see it the CPU is properly seated. Its a 12 Core cpu, so something is not right, what about the PC performance otherwise? fast/slow
how are you starting the miner?
-
It is only seeing one core because it is a vps. The 62 Mb/s was only the speeds for the first read, as was the first image. What else could be the problem? If the first read is that fast, why isn't the rest? Is there a miner where I could dedicate exact cpu usage to?
-
@Jay.f a vps is a VM. VM's are not recommended for mining. The first read was probably from the cache so it will be quicker, the following reads which will be from a different part of the disk require a disk read. The speed of the connection to the drives and the drive read speeds determine the read time.
-
@iKnow0 Thanks for the input, it mostly makes sense to me. Though I still don't understand the speeds for the first read still, http://imgur.com/a/yIC10.
