Just curious how many cards people have managed to fit into a milk crate style rig?
With risers its really all up to your MB. A milk crate is enough room to spread a decent amount apart. |
|
|
|
anything over 2000000 and mine crashes. x64 bit launches and stops closes window.
You sure you're on the newest version (hp7)? I just tested 10mil on x64 and it worked fine. What kind of CPU are you using? I have an i7 3820, and I have been reporting this problem since at least hp4. I used to be able to go up to 4M just fine, and anything over that crashed - but with hp7, anything much over 2M crashes. I7 3930 |
|
|
|
|
anything over 2000000 and mine crashes. x64 bit launches and stops closes window.
|
|
|
|
|
If we donate on the day its released will we get access?
|
|
|
|
Port is open (I assume it is open on windows by default). Nodes are added, but still wallet is not syncing
same shit happening to me, on two different comps, two different places, different routers that always worked with every other wallet.. +100500 firewall is off, the port is open, but no synchronization!!! the author answers?? when?? How many nodes does it show its connected to? If it reaches 100+ then its working. |
|
|
|
|
Any news on progress? Projected release is it still on time?
|
|
|
|
I've signed up at kcmocolo/J. Morgan for hosting some Single SC's, though they haven't been delivered there, yet. It looks like they're affiliated with Joe's Data Center ( joesdatacenter.com). I heard about Joe's DC years ago, and they seem to have a good reputation. As for Josh hosting out of that data center, I think it makes sense he would choose a local data center given the choice. Whether Josh is involved with this new J. Morgan & Associates hosting service or not, I don't know. If he is, that would be a plus. Josh is already hosting at one of the mentioned data center of which he owns. Three of the data center addresses mention on the KCIX site are literally within walking distance from each other. It would take less than ten minutes to walk from any one of them to the other two and BFL's original address, physically touching all four buildings. The only thing that I haven't figured out YET is how BFL is able to collect the mail addressed to 25 E. 12th St. without a suite number. Maybe mail just goes to building? Sorted there. |
|
|
|
Prices will be 2.25BTC below 5 orders or 2.15 for 5 or more, the extra costs from the 1.99BTC they are sold for is to to cover postage, time and effort.
LOL there are extra costs plus overpriced? |
|
|
|
Terrahash, we really need an update now, especially for assembly order which has chips already shipped (me) - Where should chips be shipped to? - Are you still sticking to two weeks turnaround time from the time when you received chips? Would your board design and assembly line be ready? Assuming two weeks for chips in transit, that means I should be mining in FOUR weeks? (finger crossed  Don't expect update. |
|
|
|
|
Reasonable priced and end of august. If its not preorder i think a lot will be intrested.
|
|
|
|
|
One computer has 100+ nodes other has 4.... i dont get it.
|
|
|
|
|
edit figures after i typed it, then it connects to node
|
|
|
|
-hp6 released!
Lots of changes in this release. Here's a list of notable changes:
* Added fast divisibility tests before doing the expensive Fermat's test
* Lots of other small optimizations
* Introduced a new experimental tuning parameter "sievepercentage". Default value is 10, minimum is 1, maximum is 100.
* Added new RPC command "getchainspermin"
* Added the following information to "getmininginfo": chainspermin, difficulty, sievepercentage, and sievesize
* Attempt to fix the random crash while mining
My PPS on mainnet went up 23% with this release with difficulty >= 9 on mainnet. This release attempts to fix the random crash while mining. I'm not sure if it's actually fixed because I have heard both positive and negative reports. The crash is more likely with high number of cores. 16 and 32 core machines are suffering the most.
The "sievepercentage" parameter is there for people to experiment with. It limits how many base primes are used to filter out candidate multipliers in the sieve. 8% seems optimal for testnet but I have no idea about mainnet.
This build is doing horrible for me. Dropped down to 9 blocks last hour, and 5 this one (almost at the end of the hour). Was getting between 8 and 20 the last build, even after diff 9. Gonna give it one more hour of variation, then switch back. My servers restart primecoind upon crashing, so could the reduction be from multiple crashes? Any explanation? Can we change "sievepercentage" from debug console? My primecoin.conf is not working no matter what I try. I've literally tried everything. Same here on not getting primecoin.conf to work. But it's probley me. |
|
|
|
Sorry for dumb question. How to i add node?
In your spots.conf file in the %appdata% addnode=the ip Just add that and the end of the text file So go into appdata find the spots folder. After that i dont see a spots.conf do i just create a txt file named spots.conf? Do i need any command to get it to import it after? |
|
|
|
|
Sorry for dumb question. How to i add node?
|
|
|
|
|
I put in front of a fan i have aimed at a GPU rig, with that they haven't got hot to touch once. Not the most power efficient cooling wise. But if you have a GPU rig still running works great.
|
|
|
|
did you hard coded that path of primecoin.conf ?!
i changed the path of data folder in my run.bat so the blockchain and wallet is in some other places ( in my D drive ).
I make a primecoin.conf there and changed the sievesize to 2milion, but when i run the program, sievesize is still 1milion.
Same here mine says the default. |
|
|
|
-hp6 released!
Lots of changes in this release. Here's a list of notable changes:
* Added fast divisibility tests before doing the expensive Fermat's test
* Lots of other small optimizations
* Introduced a new experimental tuning parameter "sievepercentage". Default value is 10, minimum is 1, maximum is 100.
* Added new RPC command "getchainspermin"
* Added the following information to "getmininginfo": chainspermin, difficulty, sievepercentage, and sievesize
* Attempt to fix the random crash while mining
My PPS on mainnet went up 23% with this release with difficulty >= 9 on mainnet. This release attempts to fix the random crash while mining. I'm not sure if it's actually fixed because I have heard both positive and negative reports. The crash is more likely with high number of cores. 16 and 32 core machines are suffering the most.
The "sievepercentage" parameter is there for people to experiment with. It limits how many base primes are used to filter out candidate multipliers in the sieve. 8% seems optimal for testnet but I have no idea about mainnet.
This build is doing horrible for me. Dropped down to 9 blocks last hour, and 5 this one (almost at the end of the hour). Was getting between 8 and 20 the last build, even after diff 9. Gonna give it one more hour of variation, then switch back. My servers restart primecoind upon crashing, so could the reduction be from multiple crashes? Any explanation? It seems that the total number of blocks found per hour changed drastically since diff 9. It now is around 3-4 blocks per minute as far as I can tell, while it was 5-6 per minute a few hours ago.. It seems difficulty is now getting where it should be.. PPS went down as well it seems; used to have 400k pps / 100 machines, now its 200k pps / 100, but still finding more than 3 blocks per 200k pps new style.. Definately getting harder though I'm in PPS envy. |
|
|
|
|
Anyone else seeing drop in PPS?
|
|
|
|
|
Show Posts
