Definitely do not like seeing this at 13 bux a pop, I bought all mine at 14 bux, so I hope it stops, balances out and then gets its butt up , Sale price would be under 9 I think for me, if it kept going down steady for a week, I believe in the concept and I hope it keeps picking up speed and hopefully this is the fourth of july weekend low trading ccausing these issues, and people still sellling out.
July 4th the volume is actually not that low:  |
|
|
|
I don't buy them back, never. I just mine them. My question is always whether I should hold on to the coins I mined because they have the potential to go to $100, or whether I should sell them before they go to $0.
If you're just mining, and not speculating at all, then just sell them as you get them. Yes, that's what I should have done. When the price was at 30, I already mined 2 BTCs (regrettably didn't sell). Now I have to sell 5 BTCs in order to get $60. Just sold 1/3 of all my BTCs for $13.59 on average. Will continue to sell at least 1/3 while mining. |
|
|
|
|
I don't buy them back, never. I just mine them. My question is always whether I should hold on to the coins I mined because they have the potential to go to $100, or whether I should sell them before they go to $0.
|
|
|
|
Stay far away... read the reviews.
My advice on PSU's: If its not Enermax or Corsair don't buy it. Always remember a bad PSU can destroy your entire computer.
add seasonic |
|
|
|
|
I have my belief in BTC myself but I'm not going to argue against the market (well, if the market crashed due to some hacking, that's a different story). While I'm typing, the price continues to fall. Too bad it'll take some a couple of hours for my funds to be transferred.
|
|
|
|
|
then what's your guys' target price?
|
|
|
|
|
if anybody is familiar with this basic investment concept. Now my question is what's your stop loss? You're holding BTCs because you either bought them or mined them. Either way, do you set any stop loss?
For me, I'll probably sell all my BTCs if the price goes below $10.
|
|
|
|
|
re the no dummy plus thing, does it work with remote desktop (RDP)?
|
|
|
|
|
Not stale rate, but rejection rate, which you can calculate using the stat shows in your miner. My case, for example, [8053 Accepted] [119 Rejected], so the reject/accept ratio is 119/8053=1.47%.
I believe this is also pool related:
deepbit: about 0.6%
btcguild: about 1.5%
slush: will test next...
|
|
|
|
|
Out of curiosity, why does it take 120 confirmations, vs. slush only takes 100 confirmations?
Anyway, it's a great pool.
|
|
|
|
|
This is important for CPU miners, since their payout is very small. All major pools (deepbit, btcguid, slush) should switch to pay in full.
|
|
|
|
Will one of you guys who are running at 300 mem clock and worksize=256 give 225 mem clock and worksize=128 a try, and let me know your before and after results.
I don't have any 5830s, but all 58xx cards should behave similarly. On my 5870s I noticed that below ~250 mem clock worksize=128 works better. In fact, the optimal settings I've found we're at mem=186, worksize=128. That gives a few Mhash/s more than worksize=256 and mem anywhere between 250 and 400. The conclusion I came to with the 6870 was that the sweetspot was between 180 and 240. I was thinking the 5800s should be similar. There seemed to be a nice spike between those values, then below 180 the hash rates fell off rapidly. Did you find a similar pattern? Pretty much spot-on. At worksize=128, between 180 and 250 the hashrate varies by a couple Mh/s, below 180 it drops fast and above 250 it starts decreasing slowly. By mem clock 300, worksize=256 is ~10 Mh/s faster and peaks at mem clock 354. But the worksize=256 peak @ mem clock 354 is still about 5 Mh/s lower than the worksize=128 peak at mem clock 186. If this is not a dedicated rig though, then there is one issue with using mem clocks as low as ~200. Any load on the video card, such as playing video or flash, will lower the hashrate a lot more than at higher mem clocks. Same observation with 5830. The only difference here is worksize=256 peak @ mem clock 354 is about 5 Mh/s faster than the worksize=128 peak at mem clock 186. |
|
|
|
|
seems always related to 2+ video cards?
|
|
|
|
Will one of you guys who are running at 300 mem clock and worksize=256 give 225 mem clock and worksize=128 a try, and let me know your before and after results.
I don't have any 5830s, but all 58xx cards should behave similarly. On my 5870s I noticed that below ~250 mem clock worksize=128 works better. In fact, the optimal settings I've found we're at mem=186, worksize=128. That gives a few Mhash/s more than worksize=256 and mem anywhere between 250 and 400. The conclusion I came to with the 6870 was that the sweetspot was between 180 and 240. I was thinking the 5800s should be similar. There seemed to be a nice spike between those values, then below 180 the hash rates fell off rapidly. Did you find a similar pattern? Only work for worksize=128. My best setting (5830) is memclcok = 300 with default worksize (SDK 2.1 + poclbm), which gave me 6 mhs more. Of course, setting memclock to 200 will lower the electr bill.  |
|
|
|
|
375W is enough for me with 5830
|
|
|
|
|
6870 sells at 210 on newegg, while 5830 sells at 110 (OOS now). Clearly it's hard to get both cards for a simliar price.
|
|
|
|
|
Are you ready? Just wondering what would be the difficulty jump after that...
|
|
|
|
more pictures please
Yes, more pics pls |
|
|
|
|
Show Posts
