Where to mine with 36Ths 24/7?

[wmabern]

Questions/answers about the pool would be best in the pool thread
So anyone with the same question might see the answer
https://bitcointalk.org/index.php?topic=789369.0

LOL. Agreed.
I will be moving my miners back to Kano in a couple weeks after my current experiment. It will be nice to use a node closer to home. NYA should be very good for my ping time. See ya'll again soon!

[1714849317]

1714849317

[1714849317]

1714849317

[1714849317]

1714849317

[sarakuka]

My final decision is I will leave my miners at first pool kano.is for one month and will update.

These are my configuration of my miners atm and will be for one month.

0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25

Thanks

Depending on where you are located, kano's pool has other locations that may be a better option for you. The best way to figure out which one works best (i.e.: is closest) for you is to ping them and check the response times.

Kano's nodes are:

• US: stratum.kano.is
• US: nya.kano.is
• DE: de.kano.is
• SG: sg.kano.is
• JP: jp.kano.is
• NL: nl.kano.is

and all of the nodes listen on these ports:

• 3333
• 80
• 81
• 443
• 8080

in case you have issues getting through firewalls.

I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:

Code:

ping -c 10 stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms

--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms

Code:

ping -c 10 nya.kano.is
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms

--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms

So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.

edit: added port info

I'm gonna do this today and will let you know.

You guys are the best.

Thanks

[sarakuka]

My final decision is I will leave my miners at first pool kano.is for one month and will update.

These are my configuration of my miners atm and will be for one month.

0 stratum+tcp://stratum.kano.is:3333
1 stratum+tcp://stratum.antpool.com:443
2 stratum+tcp://stratum.antpool.com:25

Thanks

Depending on where you are located, kano's pool has other locations that may be a better option for you. The best way to figure out which one works best (i.e.: is closest) for you is to ping them and check the response times.

Kano's nodes are:

• US: stratum.kano.is
• US: nya.kano.is
• DE: de.kano.is
• SG: sg.kano.is
• JP: jp.kano.is
• NL: nl.kano.is

and all of the nodes listen on these ports:

• 3333
• 80
• 81
• 443
• 8080

in case you have issues getting through firewalls.

I live in the US on the east coast so I'd consider using stratum.kano.is and nya.kano.is:

Code:

ping -c 10 stratum.kano.is
PING stratum.kano.is (104.194.28.194): 56 data bytes
64 bytes from 104.194.28.194: icmp_seq=0 ttl=54 time=100.933 ms
64 bytes from 104.194.28.194: icmp_seq=1 ttl=54 time=100.200 ms
64 bytes from 104.194.28.194: icmp_seq=2 ttl=54 time=100.376 ms
64 bytes from 104.194.28.194: icmp_seq=3 ttl=54 time=100.377 ms
64 bytes from 104.194.28.194: icmp_seq=4 ttl=54 time=100.882 ms
64 bytes from 104.194.28.194: icmp_seq=5 ttl=54 time=100.505 ms
64 bytes from 104.194.28.194: icmp_seq=6 ttl=54 time=100.561 ms
64 bytes from 104.194.28.194: icmp_seq=7 ttl=54 time=100.863 ms
64 bytes from 104.194.28.194: icmp_seq=8 ttl=54 time=100.172 ms
64 bytes from 104.194.28.194: icmp_seq=9 ttl=54 time=100.743 ms

--- stratum.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 100.172/100.561/100.933/0.268 ms

Code:

ping -c 10 nya.kano.is
PING nya.kano.is (104.207.132.42): 56 data bytes
64 bytes from 104.207.132.42: icmp_seq=0 ttl=53 time=34.476 ms
64 bytes from 104.207.132.42: icmp_seq=1 ttl=54 time=34.157 ms
64 bytes from 104.207.132.42: icmp_seq=2 ttl=54 time=34.907 ms
64 bytes from 104.207.132.42: icmp_seq=3 ttl=54 time=34.257 ms
64 bytes from 104.207.132.42: icmp_seq=4 ttl=54 time=35.185 ms
64 bytes from 104.207.132.42: icmp_seq=5 ttl=54 time=34.080 ms
64 bytes from 104.207.132.42: icmp_seq=6 ttl=54 time=34.635 ms
64 bytes from 104.207.132.42: icmp_seq=7 ttl=53 time=33.699 ms
64 bytes from 104.207.132.42: icmp_seq=8 ttl=54 time=34.291 ms
64 bytes from 104.207.132.42: icmp_seq=9 ttl=53 time=33.556 ms

--- nya.kano.is ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 33.556/34.324/35.185/0.477 ms

So for me it would be better to use nya.kano.is, but I would then put one of the other nodes as a backup pool, and then for my third pool pick a different pool altogether, and now knowing what I know about p2pool, I'd use one of the public p2pool nodes.

edit: added port info

Best ping i get is from de.kano.is with time=37 ms

Should i configure it with stratum.de.kano.is:3333 ?

[sarakuka]

This is my last configuration. I have the best ping with de.kano.is then nl.kano.is then stratum.kano.is that way I configured.



Thanks