Latest posts of: rethaw

What do you guys think about buying used Xeons versus renting servers?

Had a xeon running for two weeks, found no blocks at current diff. :sad:

but you can still pool mine, right?

Of course.

Quote from: adam3us on January 26, 2014, 01:35:47 PM

There are grey-goo outcomes if you are not careful with even something as constrained as an extrospection op code to existing language. There will be whole classes of not yet imagined grey goo opportunities lurking in a full TC language. You cant easily systematically defend against whole classes of such issues without intentional constrained language.

I figure the grey goo nightmare is an unspoken goal of Ethereum. Has Vitalik written on this elsewhere?

Quote

"Best bet is to get some implementation. Most services fail due to lack of traction, not failure to scale."

can you elaborate on this ? what do you mean by lack of traction ?
thanks

Lack of traction means people not choosing to use it, and come back to it. If Mt. Gox had waited until they had a full featured socketed API, or DDoS protection, they may not have become such a popular exchange, for example. I would call this the businessman's answer.

Quote from: maaku on February 03, 2014, 07:19:32 AM

This is so very much the wrong way to ask the question. Figure out what your orderbook design will be, and how you will make it consistent at scale. Your strategy for that will determine what databases or locking frameworks you intend to use, and then look at which languages integrate best with that infrastructure.

This is the engineer's answer.

My electricity costs don't warrant it, but who doesn't love bear metal?!

Quote from: DeathAndTaxes on January 30, 2014, 09:16:57 AM

That was a random jumble of buzz words and phrases saying absolutely nothing.

This should point you in the right direction.

Quote from: empoweoqwj on February 01, 2014, 03:15:46 AM

If you are talking security, the language is relatively unimportant. Its whether you understand the security risks and guard against them. You can achieve this in several languages. For a speedy trading engine, certainly C.

Best bet is to get some implementation. Most services fail due to lack of traction, not failure to scale.

Quote from: raveldoni on December 29, 2013, 05:04:16 AM

Sorry to bother you again. I have one more question:

If I want to make some changes like value of 'genproclimit=1' how can I do it?

It's this part of the command, just change it to what you want to use.

Code:

screen ./primeminer -poolip=54.200.248.75 -poolport=1337 -pooluser=Acrenf7WMZ3yFc7xkdbF8rGuuLw36Bkknr -poolpassword=PASSWORD -genproclimit=1

I suppose most of these directions apply to any VPS with a Debian or Ubuntu image.

As far as optimizing solo mining... could you be more specific? The point of pooled mining is to reduce variance, so for many, solo mining is long bet.

Quote from: achillez on December 14, 2013, 05:40:47 AM

I'm curious - does digitalocean still limit the max # of instances to 5? This is what I experienced last time - they wouldn't support primecoin mining.

They will increase your instance limit if you ask them.

Quote from: raveldoni on December 14, 2013, 05:48:00 AM

Sorry for a noob question, How can I go back to mining screen after I exit by pressing Ctrl + A and D?

Code:

screen -r

Added to the OP.

Quote from: uk1 on December 09, 2013, 01:19:32 AM

how many cores does each package have?

The number of cores is equal to the number of CPUs.

I have 4 v2 M-boards and 1 v1 M-board. Contact me if you're interested.

Quote from: eadmanday on December 03, 2013, 09:36:28 PM

I am trying to get this installed on an online AWS server. like digital Ocean. I have compiled everything and i am trying to run everything. but when i check the mining, i get little to nothing.

2013-12-03 21:30:27 primemeter 86321 prime/h 1368657 test/h 0 5-chains/h 0.012314 chain/d
2013-12-03 21:31:28 primemeter 110984 prime/h 1721939 test/h 59 5-chains/h 0.016618 chain/d
2013-12-03 21:32:29 primemeter 114366 prime/h 1822189 test/h 0 5-chains/h 0.016676 chain/d
2013-12-03 21:33:29 primemeter 105579 prime/h 1629647 test/h 0 5-chains/h 0.013099 chain/d
2013-12-03 21:34:29 primemeter 105275 prime/h 1566544 test/h 0 5-chains/h 0.014631 chain/d

it seems like its very low for the server.

also i have changed my rpcuser to my beeeeer address and password. was that where i mine for a pool? or could i put my wallet address in the config somewhere?

If you want to pool mine, you need to use a pool miner, not the full client. There are a number of threads on this, check out this one! https://bitcointalk.org/index.php?topic=252944.0

Check out peercoin and primecoin, both implemented by Sunny King.

Just wanted to say, someone appears to be mining using the address in the OP. Though I appreciate the donation, remember to change that address to your primecoin address!

Quote from: Amph on November 30, 2013, 03:03:58 PM

how can you mine such thing in a POOL? cuz cgminer don't work with this

Check out this thread about primecoin mining using a VPS here. There are still limited options for pools, though.

I've only used it against beeeer.org.

Bonus points: turn it into a service that starts at boot so you can clone a bunch of droplets!

First, write a miner script:

Code:

cd ~
echo '
cd /root/primecoin/src
screen -d -m ./primeminer -poolip=54.200.248.75 -poolport=1337 -pooluser=Acrenf7WMZ3yFc7xkdbF8rGuuLw36Bkknr -poolpassword=PASSWORD -genproclimit=1' > startprime

chmod +x startprime

Now make the service that will keep it alive:

Code:

echo '
#!/bin/bash

until /root/startprime; do
  echo "Restarting miner">&2
  sleep 1
done' > primeservice
chmod +x primeservice

Now you can edit crontab to include this service to start at reboot. Type `crontab -e`, and in the last line of the file add:

Code:

@reboot   /root/primeservice

Now reboot the droplet with `sudo reboot`. When you've logged back in, check to see if it worked by sending `screen -r`. This should open the miner info.

You can then `sudo poweroff` the droplet and take a snapshot. This snapshot is then used when creating a new droplet!