Kano it's not to compare to other pools but to compare with different GPU settings. Not useful to compare stats on 2 48 hr runs when the share chain difficultly is changing during the 48 hrs (I think that's what DAT was saying). It should still be useful to compare U of several of the same cards at different settings though - assuming auto-gpu isn't throttling them...someone please turn down the sun in FL so I can get some good numbers
As long as your miner is reporting MH/s accurately, the U: value isn't worth taking note of.
U: is random.
Same card same time same temperature same cgminer settings but: different block headers will give different values - the shorter the test time, the bigger the variance ... just like block mining
Of course rejects are worth noticing but that's a different issue ...
I would just like to double check. Got some strange results and it likely is due to the variable share difficulty but I just want to nail it down. Had two rigs started roughly the same time (within 30 sec). Involved over 11200 difficulty 9 shares so ~100K difficulty 1 shares. First rig had higher MH/S but second rig had higher A. They had different worksize.
Now 99% sure it is due to variable share difficulty but they should have been adjusting to new share difficulty at the same time and thus it shouldn't affect stats.
...
Regarding A: - well they are still hashing different block headers even at the same time - so A: will of course differ between the two.
The time field will vary, the coinbase may vary (not sure though since p2pool creates the coinbase, not bitcoind) when a new txn comes in even the merkle root will vary between 2 getworks one before and one after, and same for the coinbase txn each time a new share comes in (every 10 seconds)
Think of it this way - if they were actually hashing the same block header, they'd find the same pseudo shares and thus you'd be wasting double the power on the same result.
Though after 100K diff 1 shares you'd expect them to be close ... if the hash rates were the same ... but get someone like Meni to do the actual stats calculation of the variance
(and of course two cards exactly the same can get different hash rates as is obvious)
As for pseudo-share difficulty - I'm not sure how and when that changes - though that should be that python code above that JayCoin pointed out.