I have a LTC wallet set up now and have signed up to lc.ozco.in. Mainly because I think graet seems like a stand up guy. Not sure which (if any) other LTC pools I should check out. Opinions?
You will probably find this useful: https://github.com/coblee/litecoin/wiki/Comparison-of-mining-poolsWhat's everyone's favorite scrypt mining program? I am testing ArtForz's mod of cpuminer and plan to try minerd-amdfam10 too. I've got quite a range of cpus. Mostly 1-3 years old, sempron and core2duo.
ArtForz's miner is currently the state of the art, as long as it is compiled with the right optimization options. I am personally working on further performance improvements... stay tuned. And finally, what to do with the LTC? I see a market on BTC-E... anywhere else?
BTC-E is currently the most popular exchange, but there are others: http://cryptoxchange.com/https://vircurex.com/
|
|
|
Yes, I know about those links, but sadly most of the hash rates reported there appear to be suboptimal. I am interested in the top hash rate a thread can do per GHz, not in real-life situations where the miner is only using spare cycles.
|
|
|
Graet, may I ask the exact clock speeds and top hashrates per thread on those two rigs?
I'll have to check, but basically they are btc mining rigs and i get the shakes if they are down Ahah, yeah, I know that feeling! Let me know if you can get the exact clock speeds and hashrate per thread, these days I'm working on further optimizing ArtForz's minerd, and I'm trying to collect as much performance data as possible, for reference.
|
|
|
Using CPU instead of GPU: I wouldn't really consider it only on the pro side. It's really double-edged, can be considered both as pro and as con.
Could you please explain why you see it as a possible con?
|
|
|
I'm not sure why it is, even compiled in 64-bit binaries for windows it has tended to be slower. The Intel compiler may just choke on the scrypt code in terms of optimizations. I guess you could always try compiling with mingw-w64.
I tried out the latest icc for Linux, and it's strange, but the resulting binary is indeed much slower than the one produced by gcc with the same optimization flags. Has anyone tried compiling minerd with MinGW for 64-bit Windows?
|
|
|
i use same miner on amd athlon2 and amd phenom6 i get ~3Khash/per thread so the athlon gets me ~6 phenom ~18 this is at standard clocks ets, i say ~ because reported hashrate fluctuates
Graet, may I ask the exact clock speeds and top hashrates per thread on those two rigs?
|
|
|
I'm glad you asked. There appears to be much confusion about how to obtain the best hashrate. Let's see, how many khash/s do you currently get, and at what clock speed? As I recently wrote on the Liteco.in forum, I have tested the miner on a Core 2 and on a Phenom II, and on both I get the same hashrate/clock ratio, about 1.015 khash/s per GHz. That is, I have 1.63 at 1.6 GHz on the Core 2 and 3.55 kh/s at 3.5 GHz on the Phenom II. (All this compiling ArtForz's cpuminer with gcc -O3.)
(By ArtForz's miner I mean https://github.com/ArtForz/cpuminer) I have heard that i7's can do slightly better than that, but it is my understanding that on 64-bit platforms it should almost always be possible to get at least as many khash/s as GHz (per core, of course). By the way... many report that the AMD-optimized miner for Windows linked by the OP is faster than the i7-optimized one... on i7's! If that's true, don't you think it's a bit confusing for newcomers?
|
|
|
avoid running minerd on windows altogether, even if it runs it tends to be much slower
Personally I have never tested minerd under Windows (I don't have a Windows box), but if what you say is true, does anybody have an explanation for this? The performance should not depend on the operating system (unless of course you run 32-bit software on top of a 64-bit arch).
|
|
|
I have put together a mining calculator that relates hash rate to the probability of finding a block. Enter your hash rate here to try it out: http://www.litecoinpool.org/calcI hope solo miners like you will find this useful. Neat! Would you care to open-source it? It's actually a very simple script, the only thing that requires some thought is the formula to compute the probability. Here it is: prob("a block in [time]") = 1 - (1 - 1 / (2^32 * [difficulty]))^([hashrate] * [time]) The graph is made using Google Chart API ( http://code.google.com/intl/en-US/apis/chart/image/docs/gallery/line_charts.html). Just look at the image's URL to see how it's done.
|
|
|
i have 4 cores but i think i'm only using 2... I have 2 threads which i think is the same thing.
Yes, basically it's the same thing. hopefully i'll find a block in a few days!
I have put together a mining calculator that relates hash rate to the probability of finding a block. Enter your hash rate here to try it out: http://www.litecoinpool.org/calcI hope solo miners like you will find this useful.
|
|
|
Yeah, I'm always sad when a project shuts down, and this is no exception. I hope a new (and possibly "jerkish" ) pool will open to fill up the gap. Even if interest in the coin appears to have faded a little bit lately, Litecoin is still the best alt currency out there.
|
|
|
so i have the litecoingui and minerd and all its accompanying files in the same folder and have been successfully pool mining for about a week now. i wanna try to solo mine for two weeks or so but i have a couple of concerns. 1. How do i know if its working? i've run it for about an hour or so and it just says "mining started" i understand there'd be no shares, but is it going to give any indication that its doing what its supposed to? 2. Does it matter that my mining computer is sometimes offline for a few hours sometimes? this is my main concern. Its not offline often but right now my isp SUCKS and drops connection every few days. will that restart the process?
anyway thanks for your time!
1. If you are using cpuminer and you are seeing the hashmeter output, everything should be working fine. 2. Blocks are discovered randomly, so you do not lose your progress when you stop your miners. You can estimate the time necessary to find a block using this calculator: http://allchains.info/calc.htmlAt the current difficulty, you can average a block every 24 hours with about 45 khash/s.
|
|
|
The lithium ion batteries common in cell phones, cameras, and laptops ( the 18650 cell is most common in laptop batteries ) have rated lifetimes in terms of the number of charge/discharge cycles and actually benefit from fewer "deep" discharge cycles. Leaving them on charge with an intelligent charger ( as most are ) shouldn't be an issue if heating is not a problem. http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteriesYep, I live in a hot climate and I keep my laptop's (li-ion) battery in the fridge most of the time.
|
|
|
I would be curious to know if we could mine LTC on a Raspberry PI. http://www.raspberrypi.org/ It's only $25 and really low power. And runs linux. :-) Sadly the $25 model has no Ethernet controller... but it has a HD GPU
|
|
|
btc-e only have a 24h chart
While we wait for molecular's graphs to be back up, I have put together a simple 7-day chart: http://www.litecoinpool.org/charts#marketThis is probably not as accurate, but it's better than nothing.
|
|
|
For all those who wanted to play with the Javascript API but didn't know where to start: I have written a simple widget that allows visitors to start/stop the miner, and uses a cookie to make the decision persistent. http://jsfiddle.net/pooler/XB5Fg/This is an opt-out version, i.e., the miner is auto-started by default. An opt-in version can easily be obtained by changing the condition in the "if" at the end of the code.
|
|
|
A question about the API: Currently the API is like this (in php print_r() format): {code} All the workers' names include a dot, and it's 500 if I use the data like this: echo $lp["workers"]["user.worker"]["hash_rate"];
How to use it correctly? The dots should not be an issue if you use associative arrays. The following code works for me: $api = json_decode(file_get_contents("http://www.litecoinpool.org/api?api_key=my-api-key-here"), TRUE); echo $api["workers"]["pooler.1"]["hash_rate"];
|
|
|
Difficulty is increasing... +15%!
I have just noticed a curious fact: at difficulty 1, the expected daily earnings in coins/day equal the hash rate in khash/s, with an error of less than 0.6%!
Suppose your hashing speed is 1 kH/s: you will compute 86,400,000 hashes a day. At difficulty 1 the probability of finding a block is 2-32 per hash. Since a block is worth 50 coins, your expected daily earnings will amount to 86,400,000 / 4,294,967,296 * 50 = 1.00582838058
This means that you can estimate your daily income by simply dividing the hash rate by the difficulty. Now isn't that remarkable?
|
|
|
|