2018-06-30 01:16:52

Ninja
2018-06-30 01:17:11
what

Ninja
:grin:
2018-06-30 15:59:34
New miner code "works". At half the rate of the old one and produces nothing but invalid shares.

Fireduck
2018-06-30 15:59:51
So I guess rate is really 0% of the old one

Fireduck
2018-06-30 16:02:36
lol good work duck

Shoots
2018-06-30 16:04:32
Thanks

Fireduck
2018-06-30 16:05:53
Whatever asshole made this pow was not worried about ease of programming

Fireduck
2018-06-30 16:12:03
didnt you suggest he may have been drunk?

Shoots
2018-06-30 16:15:52
no no, the explorer was written by a drunk

Fireduck
2018-06-30 16:15:55
the pow just a jerk

Fireduck
2018-06-30 16:17:04
what is the POW algo?

Shoots
2018-06-30 16:18:46
6 passes of reading and hashing

Fireduck
2018-06-30 16:18:54
spinning around 3 times really fast in your rolly chair.

Clueless
2018-06-30 16:19:38
would have made it more but each pass has an associated proof in the block header

Fireduck
2018-06-30 16:19:44
and was trying to keep those reasonable

Fireduck
2018-06-30 16:21:38
spinning too much makes you dizzy

Clueless
2018-06-30 16:22:00
which is why 128-bit hashes in those proofs

Fireduck
2018-06-30 17:07:59
does GPT vs MBR for formatting a drive have any bearing on snowblossom performance?

THX 1138 4EB
2018-06-30 17:13:25
Amost certainly not

Fireduck
2018-06-30 19:01:22
woo! produces valid shares now

Fireduck
2018-06-30 19:09:09
ok, it is same speed when not involving ram

Fireduck
2018-06-30 19:09:52
wtf

Fireduck
2018-06-30 19:11:05
ram threads freaking out 24x7 problem tax cpu too much

Fireduck
2018-06-30 19:23:55
you know things have gone off the rails when you are typing Thread.yield() and hoping for better results

Fireduck
2018-06-30 19:24:11
i got a Plextor M8Pe 1TB Nvme M.2 and this adapter to put it in https://www.amazon.co.uk/Akasa-Internal-ak-pccm2p-01-M-2-Card-Interface-interface/dp/B01LZMIBVP but it hashes only 25 kh/s with CPU at 100% (i7 6700), 40, 60 or 80 threads

THX 1138 4EB
2018-06-30 19:24:31
I don't suppose there's a setting I could change that would yeild a better performance?

THX 1138 4EB
2018-06-30 19:24:33
fuck me, yield() is giving better results

Fireduck
2018-06-30 19:25:03
@THX 1138 4EB don't ask me, I've had terrible luck getting any sort of hardware to do what it should

Fireduck
2018-06-30 19:25:47
:disappointed:

THX 1138 4EB
2018-06-30 19:30:19
If the specs are correct, 85kh/s is the theoritical max for that drive

Fireduck
2018-06-30 19:34:20
how do you determine that?

THX 1138 4EB
2018-06-30 19:36:29
data rate (2000mb/s according to amazon)

Fireduck
2018-06-30 19:36:41
so 2000*1024*1024 / 4096 / 6 = hash rate per second

Fireduck
2018-06-30 19:37:02
4096 because it takes an entire 4k page to read a word

Fireduck
2018-06-30 19:37:08
and 6 passs per PoW

Fireduck
2018-06-30 19:42:29
i think this says the random read speed is 91 MB/s http://ssd.userbenchmark.com/SpeedTest/175630/PLEXTOR-PX-1TM8PeG which is so much less it must be a different value? UserBenchmark: Plextor M8Pe NVMe PCIe M.2 1TB PX-1TM8PeG

THX 1138 4EB
2018-06-30 19:42:51
91 MB/s is terrible

Fireduck
2018-06-30 19:43:49
well on user benchmarks it's one of the best scored for random read, losing only to intel optanes which top out at 176 MB/s

THX 1138 4EB
2018-06-30 19:44:00
if that were true, you'd only get 3.8kh/s

Fireduck
2018-06-30 19:44:33
I get 1800MB/s from a five year old intel nvme

Fireduck
2018-06-30 19:44:54

THX 1138 4EB
2018-06-30 19:45:02
I don't know what sort of crack that site is smoking

Fireduck
2018-06-30 19:45:06
what is this data in the 4k read column?

THX 1138 4EB
2018-06-30 19:45:31
no idea

Fireduck
2018-06-30 19:45:39
but you can get 80MB/s from a decent hard drive

Fireduck
2018-06-30 19:45:47
not random, but whatever

Fireduck
2018-06-30 19:45:53
ssd doesn't have seek time

Fireduck
2018-06-30 19:46:15
unless they are doing something super stupid like read, wait for data, read next chunk, etc

Fireduck
2018-06-30 19:46:30
you need to parallelize to saturate ssd on random read

Fireduck
2018-06-30 19:46:42
That is the only way those numbers make any sense to me

Fireduck
2018-06-30 19:47:30
i see

THX 1138 4EB
2018-06-30 19:47:36
anyways, try cranking your threads way up

Fireduck
2018-06-30 19:47:40
like 200 or 500

Fireduck
2018-06-30 19:47:49
ok, wilco

THX 1138 4EB
2018-06-30 19:51:27
i know some people have said to wait two hours but in my experience it seems to level out pretty quickly (now at 24K with 200 threads and not going up any more; will try 500 threads soon)

THX 1138 4EB
2018-06-30 19:53:51
I'd say about 2 minutes gives you a good idea in this setup

Fireduck
2018-06-30 19:54:12
if you are using memfield or depending on cache hotness that is a different story

Fireduck
2018-06-30 19:54:19
but you aren't expecting any cache hits really

Fireduck
2018-06-30 20:02:21
oh ok

THX 1138 4EB
2018-06-30 20:14:17
alas, 500 is no better than 80 :disappointed:

THX 1138 4EB
2018-06-30 20:16:03
hopefully someone can advise what makes my system depend so much on CPU to get the IO from my drive. maybe something isn't implemented well (Asus Pro Gaming Z170 motherboard)

THX 1138 4EB
2018-06-30 20:16:16
What is the CPU?

Fireduck
2018-06-30 20:17:28
i7 6700

THX 1138 4EB
2018-06-30 20:18:16
quad core, 3.4 ghz?

Fireduck
2018-06-30 20:19:13
uhh, quad core for sure but i don't know what it's frequency is

THX 1138 4EB
2018-06-30 20:19:21
that's fine

Fireduck
2018-06-30 20:19:25
should be plenty

Fireduck
2018-06-30 20:19:27
there's only one 6700, right? it's not the K version

THX 1138 4EB
2018-06-30 23:19:54
if anyone wants a fun time, the new miner is testable

Fireduck
2018-06-30 23:20:12
in the jeanluc branch, called Arktika

Fireduck
2018-06-30 23:28:16
1800MB/s?!

stoner19
2018-06-30 23:32:22
I tried, but can't run if anyone wants a fun time, the new miner is testable

AlexCrow
2018-06-30 23:32:55
can you share config example with new params?

AlexCrow
2018-06-30 23:34:05
#snow_path_list=mem_4,/var/nvme_intel/snow/chunk
#thread_list=16,256
snow_path_list=/var/nvme_intel/snow/chunk
thread_list=64

Fireduck
2018-06-30 23:34:17
you give it a list of paths and threads for each location

Fireduck
2018-06-30 23:34:28
mem_#gb means load that many gb in ram

Fireduck
2018-06-30 23:34:40
also, you need the snow file broken in 1gb chunks

Fireduck
2018-06-30 23:34:47
if I want only in memory ?

AlexCrow
2018-06-30 23:35:11
it won't be faster

Fireduck
2018-06-30 23:35:39
Sad

AlexCrow