Adjusting the abort time will not change the Hash rate unless there is something wrong either with the device or the computer's termios timing

If you are using 6.5 seconds to abandon jobs then you are aborting work too early.However the reason you have to do that may be because you are using windows and the termios timing may not be accurate.

Well, in my setup, on Windows 7, abort time changes the hash rate. the utility does not change much, but hash rate is very sensitive to abort time.

BTW, I've played with many timings, and 6.5 seconds abort time produce best utility rate. I don't care about the hash rate reported by the cgminer. Number of submitted, valid shares per minute is what makes money. So who cares if cgminer is reporting 410 or 210 Mh/s. If utility is 5.35, I'm a happy camper.

On Windows 7 (64bit), the new icarus code barely gets utility of 5. Kano, maybe you optimized too much for Unix and Windows performance took a hit.

Adjusting the abort time will not change the Hash rate unless there is something wrong either with the device or the computer's termios timing

If you are using 6.5 seconds to abandon jobs then you are aborting work too early.However the reason you have to do that may be because you are using windows and the termios timing may not be accurate.

Well, in my setup, on Windows 7, abort time changes the hash rate. the utility does not change much, but hash rate is very sensitive to abort time.

BTW, I've played with many timings, and 6.5 seconds abort time produce best utility rate. I don't care about the hash rate reported by the cgminer. Number of submitted, valid shares per minute is what makes money. So who cares if cgminer is reporting 410 or 210 Mh/s. If utility is 5.35, I'm a happy camper.

On Windows 7 (64bit), the new icarus code barely gets utility of 5. Kano, maybe you optimized too much for Unix and Windows performance took a hit.

It takes about 3 days to get Utility precision to even 1 decimal place on a single Icarus. I've seen both CGMiner and BFGMiner 2.4.4 keep well over 5 Utility on average (and I'm pretty sure there weren't any changes to this in 2.5.0)

Hey people before now I've been using Kiv's GUIminer but I got some brand new BFL singles that I need to use and I think cgminer is the most widely used and has bitforce enabled but I keep getting an error that I can't seem to find documented anywhere idk but here's the issue. When I try to open this "cgminer.exe" it opens for a second or so then shuts down doesn't mine or anything just quits. Also when I tried to build cgminer using the instructions in the "windows-build.txt" I get to the last step before running the "make" command in mingw the "CFLAGS="-02 -msse2" ./configure" command and I get and error message that I can't understand:

someone else when I made my own thread in the newb boards directed me to something he's written for ozcoin which is https://ozcoin.net/content/win7-cgminer-setup-guide. I've tried that and it works but I get the same instant shutdown thing. If someone could help me build and run this thing it would be much appreciated or if someone knows that the fix for my problems have been mentioned earlier in this or another thread it would also be greatly appreciated if you could tell me which thread so I can go and read through it and not trouble you guys any further.

The benchmark only tests with a single pre-defined getwork repeatedly.That's not a test of both cases on the Icarus.As I said above, the Icarus has 2 cases1) Find a share2) Abort before idle

Anyway, what did debug tell you?It should hopefully make it quite clear what is going on.

The reason I mentioned benchmarking was beacause you started to talk about timing issues and misbehaving hardware, so I pointed out that benchmarking should then show that. But it doesn't show that. Do you understand?

As you point out there are two cases, and only one is involved in benchmarking. From that I conclude that the problem is lurking in the second case.

I have also concluded that it is probably related to the short expiration time on p2pool, because otherwise everybody with an Icarus would experience the issue, and it doesn't seem to be that way.

The debugging info told me that the number of hashes is written in hex Apart from that not so much (yet). Looking at the source haven't gotten me far either.

I also have another more serious problem, that may or may not be related and about which I have been posting in the p2pool thread. The problem is that I get lots (like 7%) of duplicate shares from cgminer. It turns out that some of these are rolled past the expiry (=10s) by cgminer and I don't understand that issue either

Not to argue with anyone but my hashrate took 3 days to get to my expected value. It had kinda wild swings for 2 days for sure. The near instant hashrate reported what I expected. 860Mh but the average at 10 mins was 600Mh, after a day it got up to aound 800 and now it is finally nearly 844. It should hopefully land on 848 or so after long enough but above average LP could keep it down. Maybe let it run since the reported rate seems right for P2Pool and see if it evens out?

I appreciate donations at ( 1NwkQdmomQPLtdes5KuZhB1D22p7ZGRy4p )If I am helping in the CGMiner thread give it to Con or Kano. They do the work there.If you want to sign up for a coinbase account I would appreciate it if you use my referral link. US people now wire, 1% fee give or take a little for sending to your bank account. https://coinbase.com/?r=515bf6145682db9d11000028&utm_campaign=user-referral&src=

The benchmark only tests with a single pre-defined getwork repeatedly.That's not a test of both cases on the Icarus.As I said above, the Icarus has 2 cases1) Find a share2) Abort before idle

Anyway, what did debug tell you?It should hopefully make it quite clear what is going on.

The reason I mentioned benchmarking was beacause you started to talk about timing issues and misbehaving hardware, so I pointed out that benchmarking should then show that. But it doesn't show that. Do you understand?

As you point out there are two cases, and only one is involved in benchmarking. From that I conclude that the problem is lurking in the second case.

I have also concluded that it is probably related to the short expiration time on p2pool, because otherwise everybody with an Icarus would experience the issue, and it doesn't seem to be that way.

The debugging info told me that the number of hashes is written in hex Apart from that not so much (yet). Looking at the source haven't gotten me far either.

I also have another more serious problem, that may or may not be related and about which I have been posting in the p2pool thread. The problem is that I get lots (like 7%) of duplicate shares from cgminer. It turns out that some of these are rolled past the expiry (=10s) by cgminer and I don't understand that issue either

For the p2pool issue, my "guess" would be that p2pool might not be specifying the expiry time properly?If you turn on protocol debug it will tell you what p2pool is telling you to do with rolled shares and expiry.

If there is an issue with the rolltime/expiry supplied by the pool, cgminer will use --expiry and --scan-time to work out what to do.

As for Icarus - in debug mode it reports the result of each piece of work it does and how long it took to run.That should make it clear what is going on.

For the p2pool issue, my "guess" would be that p2pool might not be specifying the expiry time properly?If you turn on protocol debug it will tell you what p2pool is telling you to do with rolled shares and expiry.

If there is an issue with the rolltime/expiry supplied by the pool, cgminer will use --expiry and --scan-time to work out what to do.

As for Icarus - in debug mode it reports the result of each piece of work it does and how long it took to run.That should make it clear what is going on.

0xe280310f=3800051983 and 3800051983/10.000137=379999992.3. Not 283580784! Perhaps there is a simple resoluton after all.(BTW, it says khash/sec but clearly it should say hash/sec)[edit]no... i was wrong again. the first calculation comes directly from Hs so it will be 380MH/s by definition. the second comes from hashmeter and is measured by real elapsed time. damn.[/edit]

Regarding roll-time, the problem is not so easy as you suggest. P2pool sets the following headers:

About the duplicates. Until today I have only been able to see that a lot of duplicate hashes are submitted but now forrestv has written some code to check the timestamp (ntime) on each submitted share and write a log message if it has been increased by more than 10 seconds. On my machine it spits out error messages like this every few seconds:

Code:

2012-07-10 01:34:45.211197 > Miner digger @ 192.168.1.102 rolled timestamp improperly! This may be a bug in the miner that is causing you to lose work!

0xe280310f=3800051983 and 3800051983/10.000137=379999992.3. Not 283580784! Perhaps there is a simple resoluton after all.(BTW, it says khash/sec but clearly it should say hash/sec)[edit]no... i was wrong again. the first calculation comes directly from Hs so it will be 380MH/s by definition. the second comes from hashmeter and is measured by real elapsed time. damn.[/edit]

The 10.00 seconds is based on the counter, not the elapsed time.(this is the issue I was referring to that may need changing to deal with crappy timers on some OS's if they exist?)

The 10.000137s is elapsed time from the send work to when the abort was performed.Thus the timer on your OS is fine for that one since they match.

You will also see a "Icarus %d sent: %s" 10seconds before at ~2012-07-09 18:10:27

The hashmeter times things differently so you cannot assume it will calculate over the same time and hash count.Sometimes it will be lower and sometimes it will be higher - due to the different start/finish times of the calculation.This is only with Icarus because Icarus does not complete the full nonce range in either case:1) When it finds a share it aborts - random processing time2) When it gets close to the end of the nonce range it aborts - in your case 10s processing timeDue to this the hash meter will of course go up and down.

... also note that work returned after an LP is not counted in the hashmeter ...

First "Icarus 8" sends something and then "Icarus 5" sends the exact same thing, except that the nonces are different. They are very close in time so in this case it might be that no new work has been received yet, but it happens a lot. As I said earlier 7% of my shares are duplicates.

Expire=10 was a bug in much pool software. It did not make sense at all to have that value for anything but p2pool so the scantime is used if it is longer than expire (expire should be more like 120 seconds). This can't be creating duplicates though.

p2pool has a recent bug where duplicate work items are sent out regardless of the mining software. Anyone on p2pool?