Official YACOIN Orphan Blocks Thread - page 3.

tyrion70

legendary

Activity: 934

Merit: 1000

Quote from: ymer on May 08, 2013, 02:34:50 PM

I think the problem is low difficulty and shit location of the main node, leaves almost all of us with very high pings, the ones with good pings are getting most of the blocks.

Technically speaking there is no main node, but almost everyone connected him because of the startpost.. If I'm not mistaking a group of miners with low latency could theoretically be at an advantage. So if a few ppl with high hashpower and good latency happen to be close together no one else stands a chance..

ymer

sr. member

Activity: 308

Merit: 250

Quote from: tyrion70 on May 08, 2013, 02:34:06 PM

Quote from: ymer on May 08, 2013, 02:33:04 PM

Quote from: tyrion70 on May 08, 2013, 02:29:21 PM

The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)

Just checked again but from the 2nd location (I checked this one at work with a crap DSL connection)

I checked from home with a fiber connection where the i5 3330 miner is and the ping is 1000ms Roll Eyes

That's even worse!! Lower is better with ping... That means it takes a second to reach that IP address!! Where are u from Ymer?

I know, 1000ms = 1 second delay.

I just shutdown the miners, it's not worth at all knowing that I will not get any blocks at this difficulty because it's so low my blocks get too late.

ymer

sr. member

Activity: 308

Merit: 250

I think the problem is low difficulty and shit location of the main node, leaves almost all of us with very high pings, the ones with good pings are getting most of the blocks.

tyrion70

legendary

Activity: 934

Merit: 1000

Quote from: ymer on May 08, 2013, 02:33:04 PM

Quote from: tyrion70 on May 08, 2013, 02:29:21 PM

The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)

Just checked again but from the 2nd location (I checked this one at work with a crap DSL connection)

I checked from home with a fiber connection where the i5 3330 miner is and the ping is 1000ms Roll Eyes

That's even worse!! Lower is better with ping... That means it takes a second to reach that IP address!! Where are u from Ymer?

achillez

hero member

Activity: 874

Merit: 1000

25+ orphans, only 9 accepted

Sondey10mg

sr. member

Activity: 308

Merit: 250

6 orphans - 1 accepted
AMD phenom II x4 B55
6 hours
High speed internet - Belgium

Ping to 82.211.30.212 ~200ms Angry

ymer

sr. member

Activity: 308

Merit: 250

Quote from: tyrion70 on May 08, 2013, 02:29:21 PM

The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)

Just checked again but from the 2nd location (I checked this one at work with a crap DSL connection)

I checked from home with a fiber connection where the i5 3330 miner is and the ping is 1000ms Roll Eyes

MuErTe

newbie

Activity: 10

Merit: 0

3 orphans here

tyrion70

legendary

Activity: 934

Merit: 1000

Quote from: MrWizard on May 08, 2013, 02:28:15 PM

i can "beat" that:

Pinging 82.211.30.212 with 32 bytes of data:
Reply from 82.211.30.212: bytes=32 time=175ms TTL=46
Request timed out.
Reply from 82.211.30.212: bytes=32 time=173ms TTL=46
Request timed out.

Ping statistics for 82.211.30.212:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 175ms, Average = 174ms

50% lost packets!!!

Ouch.. hope your found blocks weren't in those packets ;-)

tyrion70

legendary

Activity: 934

Merit: 1000

The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)

MrWizard

sr. member

Activity: 252

Merit: 250

Quote from: ymer on May 08, 2013, 02:21:39 PM

Quote from: tyrion70 on May 08, 2013, 02:19:53 PM

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

ping 82.211.30.212
PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data.
64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms
64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms
64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms
64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms

Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-)

This is what I get

Code:

Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57

i can "beat" that:

Pinging 82.211.30.212 with 32 bytes of data:
Reply from 82.211.30.212: bytes=32 time=175ms TTL=46
Request timed out.
Reply from 82.211.30.212: bytes=32 time=173ms TTL=46
Request timed out.

Ping statistics for 82.211.30.212:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 175ms, Average = 174ms

50% lost packets!!!

ymer

sr. member

Activity: 308

Merit: 250

Quote from: tyrion70 on May 08, 2013, 02:26:47 PM

Quote from: ymer on May 08, 2013, 02:21:39 PM

Quote from: tyrion70 on May 08, 2013, 02:19:53 PM

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

ping 82.211.30.212
PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data.
64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms
64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms
64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms
64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms

Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-)

This is what I get

Code:

Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57

Ymer, than that is the issue.. When we both find a block you are 200ms slower in reporting it.. Because of the short timespan between the blocks it's a combination of network speed and hash speed that makes the difference. Hash speed makes u find blocks faster; network speed makes you report them to other nodes faster.

Only thing that might help is finding nodes near you and add them with addnode option.

Where are you located?

tyrion70

legendary

Activity: 934

Merit: 1000

Quote from: ymer on May 08, 2013, 02:21:39 PM

Quote from: tyrion70 on May 08, 2013, 02:19:53 PM

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

ping 82.211.30.212
PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data.
64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms
64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms
64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms
64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms

Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-)

This is what I get

Code:

Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57

Ymer, than that is the issue.. When we both find a block you are 200ms slower in reporting it.. Because of the short timespan between the blocks it's a combination of network speed and hash speed that makes the difference. Hash speed makes u find blocks faster; network speed makes you report them to other nodes faster.

Only thing that might help is finding nodes near you and add them with addnode option.

#R#a#u#t#e#

member

Activity: 65

Merit: 10

18 accepted out of 48 in 9 hours with phenom 965 (special edition with 4 broken pins i resoldered lol)
2 out of 19 with i7...
and 1 notebook wich decided to surrender Sad

ymer

sr. member

Activity: 308

Merit: 250

Quote from: clu on May 08, 2013, 02:23:54 PM

Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz, 8 GB RAM

gethashespersec
212019

this one solved some blocks during the day. 2 orphans/16 blocks,
client compiled on a linux client.

Third person with high success rate on linux.

So far no one with windows has reported high rate of good blocks.

clu

newbie

Activity: 15

Merit: 0

Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz, 8 GB RAM

gethashespersec
212019

this one solved some blocks during the day. 2 orphans/16 blocks,
client compiled on a linux client.

ymer

sr. member

Activity: 308

Merit: 250

Quote from: tyrion70 on May 08, 2013, 02:19:53 PM

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

ping 82.211.30.212
PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data.
64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms
64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms
64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms
64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms

Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-)

This is what I get

Code:

Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57
Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57

tyrion70

legendary

Activity: 934

Merit: 1000

O and Ymer, Linux definately has something to do with it..

DL-ing blockchain on Linux was 5 minutes work, on windows it went for 2 hours.. My two windows laptops have only orphanes and stales, my Linux machine has a lot of blocks

tyrion70

legendary

Activity: 934

Merit: 1000

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

ping 82.211.30.212
PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data.
64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms
64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms
64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms
64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms

Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-)

JimmyFL

member

Activity: 84

Merit: 10

for example, no block (or orphan) for me since 1hour

Topic: Official YACOIN Orphan Blocks Thread - page 3. (Read 6016 times)