Re: [6000 GH/s] Slush's Pool (mining.bitcoin.cz); TX FEES + UserDiff; ASIC tested
The problem for me is: There was a block which took a long time to resolve, and my mining rig just self-restarted during the process due to my ISP problem, and the reward for that block became 1/7 of normal reward, this has never happened with other pools 
Have had a low reward on a long block from the same issue, 5 minutes downtime = half (or less) the reward I should've got.. always seems to be the case on a 3+ hour round as well :E.
The payment system treats you the same whether you were trying to pool hop or you just happened to disconnect at a bad time. In the long term it averages out because everytime it happens to someone who isn't you, you technically benefit from their lower reward in that instance.
I still don't understand the "Suggested difficulty" field. Dose it have some thing to do with long polling? If my connection is bad do I set it higher or lower?
It means that you aim for a share with more worth. E.g. a share at difficulty 1 is worth 1 share, 2 is worth 2 shares.. and so on. The difficulty refers to the target set for your hashes. At difficulty 2 there are half as many possible hashes which would contribute a share when compared to difficulty 1.
The reason it's useful is that with a very high hashrate (>2GH/s) you'll find so many difficulty 1 shares that it'll use up a lot of communication and it floods the server with requests.. so if you look for more difficult shares, you still (theoretically) get the same rewards, but the communication with the pool server is lower.