"chainsperday" : 0.27842972
hp9, default settings... 8 cores...
nowhere near 1.7...
what am i doing wrong?
Are you sure your blockchain is up to date? It should have ~110k blocks so far. Once it's caught up, be sure to stop and restart primecoin so you have accurate info.
|
|
|
Lots of updates!
Changes include pretty much everything from the primecoin script that's been added in the last two weeks. That includes better ~/peek and start/stop scripts along with some cosmetic tweaks.
|
|
|
How long did it take to get your VPS up and running? Mine's been "pending" for almost an hour now.
|
|
|
Link is working for me. Just go to the website and click on the blacklist link in the footer. Ah, it was missing a front slash. Looks like they're not very good with HTML tables.
|
|
|
Be careful of fortatrust they are a terrible hosting provider and they will publish your personal details on their blacklist if you miss a single payment. That link is dead. Was that intentional?
|
|
|
Nice Website Y U NO in english? Get Chrome, it'll offer to translate for you.
|
|
|
Ok, now what? Primecoin doesn't count as any of the following: illegal activity, harm to minors, threats, harassment, fraudulent activity, forgery or impersonation, spam, unauthorized access, copyright infringement, collection of personal data, network disruption, or distribution of viruses.
|
|
|
how much RAM would you recommend for 8 cores?
Given that you only need ~512 MB to compile Primecoin and less than that to run it, 1GB should be fine. If you have to, you can even add a swapfile. Also: high five to Qantaqa for finding FortaTrust. Turns out "excessive CPU usage" is against Linode's TOS. So... yeeeeeaaaaah. (On a side note, did you stop/restart primecoind after letting the blockchain update? When it's catching up, it'll make wild results of 25+ chain/day that can throw the estimates off)
|
|
|
The source will of course be available at launch.
As this progresses, will an exact release time be specified or will it just be released within a ballpark time frame? For example: "August 20th at 12PM UTC" vs "the week of August 12th."
|
|
|
Anyone able to help here?
What ubuntu wallets are people using for DVC, IXC, NMC, NVC, SC, TRC?
If they have a git account, it should be pretty easy. Almost all of the *coins come with a makefile.unix. It's just about having the right dependencies installed. Take a look at the Primecoin guide in my signature. It has most of the common requirements in the apt-get install line. For installing from git, you'd use something like: git clone http://url_to_github/user/project.git cd ~/project/src make -f makefile.unix USE_UPNP=-
|
|
|
A question for Sunny King or Mikaelh:
Does the round primorial have a direct or inverse affect on the likely length of a prime chain? For example: will a larger round primorial result (on average) in longer or shorter prime chains?
|
|
|
Another tiny update.
The script now runs apt-get update before installing packages. This makes it work better with RamNode. The start and stop scripts now use [[ -n "$(pidof primecoind)" ]] to check if primecoind is running. It should no longer kill itself on accident.
|
|
|
....
I've found that if you get a node with crap performance, you can destroy the node, get your account credited, then rebuild the node elsewhere. In all, it costs ~$0.65 to destroy and rebuild, but getting 35% more performance is worth it.
Not bad at all ... the CPU is at least quite recent and it has loads of cache available, you should get around ~1.3 chains per day. You'd think so. As pointed out previously, the chains/day stat is for finding a chain with length equal to the integer part of the difficulty. It'll be less than that once you take into consideration the fractional part. (Please correct me if I'm wrong) I do average about 0.90 to 1.00 chains/day metric on each of the nodes though. Even if it's less than half of what's reported, as long as I hit ~2 blocks on each node, they pay for themselves.
As a side note, don't count on being able to use the CPU cache to full efficiency. It is shared hardware after all.
|
|
|
Not bad ... 8 cores (1 prio) ... could you please paste the output of Just wanted to know what processors are behind this. Thx one4many I have a couple of linodes as well, but they are very spread in performance. They average at about 5 cores (you only get garanteed 1 core), that perform at about half a xeon each. My 4 core ramnode performed way better (except you can't run structural CPU usage there). If I take the average in performance decline over the last weeks, I seriously doubt one should get one for xpm mining alone. You might get lucky and get a block a week, but it might just as well cost you. /proc/cpuinfo shows 8 copies of this: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz stepping : 7 microcode : 0x70d cpu MHz : 2600.056 cache size : 20480 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 36 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu de tsc msr pae cx8 sep cmov pat clflush mmx fxsr sse sse2 ss ht syscall nx lm co nstant_tsc rep_good nopl nonstop_tsc pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline _timer aes hypervisor lahf_lm ida arat epb pln pts dtherm bogomips : 5200.11 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: I've found that if you get a node with crap performance, you can destroy the node, get your account credited, then rebuild the node elsewhere. In all, it costs ~$0.65 to destroy and rebuild, but getting 35% more performance is worth it.
|
|
|
I noticed the script still sets roundsievepercentage to 30 while hp9's default changed to 70, any specific reason for this, or can i just update this?
It's fixed now. HP9 came out after my last update.
|
|
|
A well designed coin will only do better with more computing power, regardless of the source. SRC will adapt well.
Let's hope so, will throw a few khs in support of it. ~BCX~ Thanks Instead of trying to get into a corrupt economy where exchanges accept coins by bribery and their own gain, I'll just build the services to enable the economy myself. The exchange will be one step, but only one of many. Should we expect the source to be available at the same time as the client? We *nix folks don't care much for precompiled things.
|
|
|
We request that you do not release the beta to anyone that is publicly soliciting funds from others.
Thanks
haha, it's so funny watching all the greedy panicking. I only posted a reply to yager's sub offering as a joke and there were already ppl sending me pms offering a whopping 10 xpm to get the script lol. The funny part is that I have never actually donated anything yet, still waiting for the scheduled 25th of July release! 2014? It's like Hofstader's Law in action!
|
|
|
Just make sure you release the source code at the same time as the binaries and everything will be kosher.
|
|
|
so is xpm being pool mined/bot mined now
no solo's anymore ?
I barely broke even yesterday with 50 vps, but the day before was a good one... Hard to tell with such a variance, mining is really a lottery ! What are you using? ... AWS High-CPU On-Demand Instances / Medium @ $0.145 per Hour Quite expensive! I run $20/mo Linode instances. They end up coming out to $0.02737/hr for an 8-core system. As long as each box mines ~3 blocks in 30 days, I'm golden.
|
|
|
regarding haveged I can confirmed it messed up my mining. I'm chaining blocks as usual since I stopped the service.
You have been warned !
I tried service haveged stop, however when listing the status of all my services it just appears there with a plus in front of it still. How can I actually stop this? Use the following to see if haveged is running: ps aux | grep -v grep | grep haveged If it is running, use the following to stop it: To remove from startup: update-rc.d -f haveged remove I'm still looking into if haveged affects performance. At worst it should only leave performance unaffected, not make it worse.
|
|
|
|