@rico

https://i.imgur.com/eyO9zBO.png

The LBC folder have drwxrwxrwx permissions. LBC script same

@rico

That works

Intel i5 4690 @ 3.5 - 441 799 keys/s per CPU core

WSL Win10 https://i.imgur.com/bxCnm6g.png

I will be updating the LBC manual, so make sure you have a look from time to time.


duly noted


Good to see, that the VM solution under Windows has superb performance. I do not feel great pressure to push a native Win-version right now and will probably focus more on a GPU client.


Rico

"Super duper optimism" is relative. What ~2981793 seconds ago sounded "super duper", may today seem common.

http://lbc.cryptoguru.org:5000/trophies


Rico

But I think the addresses higher than 35 were searched by a modded vanitygen, in other words he searched exactly for these addresses and not for funds.

Hashrate increase wow. up to 23.29 mkeys/s

I did some small updates which now allow LBC to run on a gossamer AWS EC2 t2.micro instance:

a) pulsed operation - see http://lbc.cryptoguru.org:5000/man/user#pulsedops
b) memory friendly hexdigests while updating (from version 0.893 on)

I got this t2.micro instance for free for a whole year. It's the most flimsy piece of computing power I ever saw, so I felt challenged to make use of it for LBC.
You can get like 2.8 GKeys per day out of something like that. So next challenge will be to run LBC on my toaster.  


Rico

I thought about setting that up in the stats, but you can make a good educated guess yourself quite easily.
In the block below, I added line numbers and the "Pool: xxx" (and removed the 'o' progress indicators)

If you look at the intervals your client gets and subtract the to-value in 1. from the from-value in 2., the to in 3. from "from" in 2. etc. etc.
and if you multiply these values with "1.048576" (which is 2^20/1000000) you get basically the MKeys the pool worked through on the forefront (i.e. auto-mode operation).

So you see in 1. the client represented a capacity of about 15.3% of the pool, in 2. about 11.9% and in 12. about 9.9%
This way you can also see - at least the tendency - if the pools performance accelerates or slows down.


In case you are bored and wanted to know "how much" of the current pools capacity your client does.
It's not exact, because it doesn't take the manual searches into account which may be in completely different intervals, but it's more exact than the "Pool Performance" number in stats, which is a 24h moving average.

Therefore with this method you may see more variance in the pools performance, as there may be a spike if a big client delivered several hours of work in between your deliveries. I added also an "Activity" column to the Top30, which is a "last seen xxx ago" for the clients.

Oh and one more thing: Don't be surprised, if Pool speed will now slowly raise to ~ 40 MKeys/s  


Rico

Pool Performance: 34.34 MKeys/s