|
dreamspark
|
 |
May 29, 2014, 12:36:02 PM |
|
I see a hash rate increase on my machine - try running with number of threads = number of physical cores. Maybe even one less. It's counterintuitive but I guess taking advantage of hyperthreading negates the impact of the hardware optimisations?
the increase is not significant +30H/s (regardless of processor intel)(Win x64) AMD-error Thats significant if your running a few 100 processors...
|
|
|
|
|
DemocraticRepublicOfDave
Member


Activity: 77
Merit: 10
|
 |
May 29, 2014, 12:44:07 PM |
|
Hi All, I'm new to monero and have just upgraded my pc to 14.04 and got simplewallet going with a receiving address. I have just done my first test transfer of a small amount of MNO from poloniex to my wallet. Poloniex gave me a transaction id that can look up in the block explorer. However in simple wallet I get : [wallet xxxxx]: balance balance: 0.000000000000, unlocked balance: 0.000000000000 [wallet xxxxx]: incoming_transfers No incoming transfers [wallet xxxxx]: bc_height 61756
NOTE: transaction lookup on poloniex refers to a block hight less than 61756, so my wallet is in sync. Q. How long does it take for a transaction to be logged in the receiving wallet? I am wondering whether this wait is normal, or something has already gone wrong. Cheers Dave
|
|
|
|
|
|
dreamspark
|
 |
May 29, 2014, 12:49:46 PM |
|
Hi All, I'm new to monero and have just upgraded my pc to 14.04 and got simplewallet going with a receiving address. I have just done my first test transfer of a small amount of MNO from poloniex to my wallet. Poloniex gave me a transaction id that can look up in the block explorer. However in simple wallet I get : [wallet xxxxx]: balance balance: 0.000000000000, unlocked balance: 0.000000000000 [wallet xxxxx]: incoming_transfers No incoming transfers [wallet xxxxx]: bc_height 61756
NOTE: transaction lookup on poloniex refers to a block hight less than 61756, so my wallet is in sync. Q. How long does it take for a transaction to be logged in the receiving wallet? I am wondering whether this wait is normal, or something has already gone wrong. Cheers Dave Withdrawals and deposits to Poloniex are ropey at best. If it doesn't appear in an hour or so I'd jump in the troll box and get a mod to sort it.
|
|
|
|
|
|
equipoise
|
 |
May 29, 2014, 01:03:47 PM |
|
Hi All, I'm new to monero and have just upgraded my pc to 14.04 and got simplewallet going with a receiving address. I have just done my first test transfer of a small amount of MNO from poloniex to my wallet. Poloniex gave me a transaction id that can look up in the block explorer. However in simple wallet I get : [wallet xxxxx]: balance balance: 0.000000000000, unlocked balance: 0.000000000000 [wallet xxxxx]: incoming_transfers No incoming transfers [wallet xxxxx]: bc_height 61756
NOTE: transaction lookup on poloniex refers to a block hight less than 61756, so my wallet is in sync. Q. How long does it take for a transaction to be logged in the receiving wallet? I am wondering whether this wait is normal, or something has already gone wrong. Cheers Dave Enter "refresh" in the wallet.
|
|
|
|
Zer0Sum
Legendary

Activity: 1588
Merit: 1000
|
 |
May 29, 2014, 01:09:12 PM |
|
Hi All, I'm new to monero and have just upgraded my pc to 14.04 and got simplewallet going with a receiving address. I have just done my first test transfer of a small amount of MNO from poloniex to my wallet. Poloniex gave me a transaction id that can look up in the block explorer. However in simple wallet I get : [wallet xxxxx]: balance balance: 0.000000000000, unlocked balance: 0.000000000000 [wallet xxxxx]: incoming_transfers No incoming transfers [wallet xxxxx]: bc_height 61756
NOTE: transaction lookup on poloniex refers to a block hight less than 61756, so my wallet is in sync. Q. How long does it take for a transaction to be logged in the receiving wallet? I am wondering whether this wait is normal, or something has already gone wrong. Cheers Dave Withdrawals and deposits to Poloniex are ropey at best. If it doesn't appear in an hour or so I'd jump in the troll box and get a mod to sort it. I've had 20 poloniex withdrawals that completed in about 1 minute... And 2 that resulted in the "COMPLETE:ERROR" thing in the log (but none in 2-3 days). They check the logs and fix it... I've never had to write a Trouble Ticket.
|
|
|
|
|
DemocraticRepublicOfDave
Member


Activity: 77
Merit: 10
|
 |
May 29, 2014, 01:10:51 PM |
|
Hi All, I'm new to monero and have just upgraded my pc to 14.04 and got simplewallet going with a receiving address. I have just done my first test transfer of a small amount of MNO from poloniex to my wallet. Poloniex gave me a transaction id that can look up in the block explorer. However in simple wallet I get : [wallet xxxxx]: balance balance: 0.000000000000, unlocked balance: 0.000000000000 [wallet xxxxx]: incoming_transfers No incoming transfers [wallet xxxxx]: bc_height 61756
NOTE: transaction lookup on poloniex refers to a block hight less than 61756, so my wallet is in sync. Q. How long does it take for a transaction to be logged in the receiving wallet? I am wondering whether this wait is normal, or something has already gone wrong. Cheers Dave Enter "refresh" in the wallet. Hi, Aha - that did it. So it's manual sync between bitmonerod and simplewallet at the moment. Got it. Many thanks. This coin holds some promise I think. Cheers Dave
|
|
|
|
|
xxnirvana69xx
Newbie

Activity: 52
Merit: 0
|
 |
May 29, 2014, 01:58:48 PM |
|
If you're getting an error - your CPU doesn't have AES-NI. I detect it at build time rather than run time because it cuts down on branching.
Works on the newer FX-8320 
|
|
|
|
|
xxnirvana69xx
Newbie

Activity: 52
Merit: 0
|
 |
May 29, 2014, 02:12:11 PM |
|
There is no increase in hash rate with this Windows release compared to bitmonerod.exe Did you compiled it with the intel compiler or it's mingw/cygwin? I hope when those changes are merged to the bitmonerod / simpleminer / simplewallet and it's compilled with the intel compiler there will be a real increase in hash rate so I could continue to solo mine. I see a hash rate increase on my machine - try running with number of threads = number of physical cores. Maybe even one less. It's counterintuitive but I guess taking advantage of hyperthreading negates the impact of the hardware optimisations? I get 30H/s more running 7 threads instead of 8. Guess that works lol. Still kind of weird. I'll gladly take it though. Less cpu load (it seems), lower temps, I'm able to use my computer more easily while mining and chrome remote desktop doesn't lag to hell.
|
|
|
|
|
xxnirvana69xx
Newbie

Activity: 52
Merit: 0
|
 |
May 29, 2014, 02:48:52 PM |
|
Make that over 80H/s, but I also was running 8 threads on the last version instead of trying one less.
|
|
|
|
|
|
18602981897
|
 |
May 29, 2014, 03:28:06 PM |
|
Voting on Mintpal
|
BTC:14NxNcYM5WFG7N9NmcQioT5JxZjh5dbTET
|
|
|
|
eizh
|
 |
May 29, 2014, 04:18:55 PM |
|
There's a bug inherited by all CryptoNote coins where a transaction gets stuck in the tx_pool because of disagreements between the wallet and daemon. When this happens, your tx fails and doesn't show up on the blockchain, but you start seeing spent key image errors when trying to spend again. This will be fixed in the next release, but for now if you want to send large amounts, do it in batches less than 100 MRO.
|
|
|
|
|
GreekBitcoin
Legendary

Activity: 1428
Merit: 1001
getmonero.org
|
 |
May 29, 2014, 04:20:06 PM |
|
There's a bug inherited by all CryptoNote coins where a transaction gets stuck in the tx_pool because of disagreements between the wallet and daemon. When this happens, your tx fails and doesn't show up on the blockchain, but you start seeing spent key image errors when trying to spend again. This will be fixed in the next release, but for now if you want to send large amounts, do it in batches less than 100 MRO.
Do you think lost coins can be found in the future?
|
|
|
|
|
|
huhliki.k
|
 |
May 29, 2014, 04:30:09 PM |
|
Less (=) H/s, try somebody else.
|
|
|
|
|
|
eizh
|
 |
May 29, 2014, 04:34:04 PM |
|
There's a bug inherited by all CryptoNote coins where a transaction gets stuck in the tx_pool because of disagreements between the wallet and daemon. When this happens, your tx fails and doesn't show up on the blockchain, but you start seeing spent key image errors when trying to spend again. This will be fixed in the next release, but for now if you want to send large amounts, do it in batches less than 100 MRO.
Do you think lost coins can be found in the future? They're not lost. A transaction can only spend a limited amount of time stuck in tx_pool. You should be able to send successfully after some time with a fixed wallet.
|
|
|
|
|
|
hashnine
|
 |
May 29, 2014, 04:55:30 PM |
|
|
Careful XC anonymous coin is a scam
|
|
|
|
huhliki.k
|
 |
May 29, 2014, 04:59:56 PM |
|
-9 h/s i5-2500 CPU @ 3.30 GHz
|
|
|
|
|
blaaaaacksuit
Sr. Member
  

Activity: 280
Merit: 250
Who cares?
|
 |
May 29, 2014, 05:01:11 PM |
|
+30 Hash on fx-8320
|
|
|
|
|
|
|
|
huhliki.k
|
 |
May 29, 2014, 05:10:03 PM Last edit: May 29, 2014, 05:21:23 PM by huhliki.k |
|
Xeon x5690 = Xeon x5687 =
|
|
|
|
|
blaaaaacksuit
Sr. Member
  

Activity: 280
Merit: 250
Who cares?
|
 |
May 29, 2014, 05:10:14 PM |
|
|
|
|
|
|
|