[ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs

[zvisha]

I heard from Dogie that he will get his SP30 soon. Knowing him, he will probably do the measurements and compare the miner noise to other miners. It makes less noise then SP10, but I can not compare it to other miners because I don't have other miners.
In 110V it makes more noise then in 220V because the PSU is hotter, and most noise is from the PSU.

That sounds about right. The air coming out of the PSUs was about 15°C hotter than the air coming out of the main fans, and the PSU fans run at a much higher RPM. Maybe today I'll record an audio sample and run it through a Fourier transform.

I bet SP30 performance could probably be improved with some aftermarket modifications to the PSUs for airflow. I see the Emersons are available on ebay for reasonable prices, but I can't find the Murata PSUs there. Perhaps I'll buy a couple extra Emersons and see if I can mod them for better airflow. For example, the hole that the fan exhausts out of seems to be quite small. I'd guess that expanding those holes a bit would likely improve airflow, thereby reducing temperatures and expanding the load headroom before thermal shutdown. It also might be possible to mount a fan external to the SP30 case in push configuration in front of the PSUs. In my DC, we're already planning on setting up a sealed tunnel hot aisle config with fans forcing extra air through the SP30s. Perhaps we could set up baffles to encourage a higher proportion of the extra air to flow through the PSU. I'm looking forward to playing around with this. I think the hole widening would probably result in the biggest improvement.

Obviously, Spondoolies cannot condone or support such behavior, I know.

Don't buy emerson on ebay unless you want to recompile the source code to recognise it. We have special I2C id.

[1714282286]

1714282286

[1714282286]

1714282286

[1714282286]

1714282286

[jtoomim]

The SP30s will restart a lot for the first 24 hours or so after you plug in the PSUs. The purpose of this is to test the limits of what the PSUs can handle before they go into thermal shutdown. The SP30 brings the PSUs up to the limit of their performance, then over, and remembers the power level at which it exceeded its tolerances. During the next boot, it uses slightly more conservative settings until it never exceeds those tolerances. Personally, I think this is a pretty cool feature (although a little bit crazy). The SP30 basically overclocks itself automatically.

Disconnecting the PSU's power will reset the SP30s knowledge of the PSU's limit, and will cause this algorithm to start again. If you change the cooling conditions for your SP30, you should power cycle your PSUs so the SP30 learns its new limits.

Edit: See zvisha's reply a few posts down for the correct way to reset the PSU's limit-finding algorithm.

[jtoomim]

Don't buy emerson on ebay unless you want to recompile the source code to recognise it. We have special I2C id.

Ooh, source code?  This sounds like it could be even more fun than I thought.

once you made a bigger hole, it is usually cannot be undone easily (without replacing the whole net/panel).
could void the warranty

... I'm aware of that, thank you. I'm also aware that publishing my intent on a thread watched by several Spondoolies employees means that I can't play dumb later when things go wrong.

I think what I'll do for now is just buy one Emerson and use it to test out some mods in a fashion that only risks a $35 ebay device, and doesn't require me to take my SP30 offline while I play. If it seems like the case mods should work, I'll either recompile the source, swap the PSUs guts (along with its I2C ID), or if I'm feeling cocky, just perform the mod on all of my Emerson PSUs.

[RoadStress]

The SP30s will restart a lot for the first 24 hours or so after you plug in the PSUs. The purpose of this is to test the limits of what the PSUs can handle before they go into thermal shutdown. The SP30 brings the PSUs up to the limit of their performance, then over, and remembers the power level at which it exceeded its tolerances. During the next boot, it uses slightly more conservative settings until it never exceeds those tolerances. Personally, I think this is a pretty cool feature (although a little bit crazy). The SP30 basically overclocks itself automatically.

Disconnecting the PSU's power will reset the SP30s knowledge of the PSU's limit, and will cause this algorithm to start again. If you change the cooling conditions for your SP30, you should power cycle your PSUs so the SP30 learns its new limits.

Can't wait to test the low Iceland temperatures 

[wanna4fun]

The SP30s will restart a lot for the first 24 hours or so after you plug in the PSUs. The purpose of this is to test the limits of what the PSUs can handle before they go into thermal shutdown. The SP30 brings the PSUs up to the limit of their performance, then over, and remembers the power level at which it exceeded its tolerances. During the next boot, it uses slightly more conservative settings until it never exceeds those tolerances. Personally, I think this is a pretty cool feature (although a little bit crazy). The SP30 basically overclocks itself automatically.

Disconnecting the PSU's power will reset the SP30s knowledge of the PSU's limit, and will cause this algorithm to start again. If you change the cooling conditions for your SP30, you should power cycle your PSUs so the SP30 learns its new limits.

Can't wait to test the low Iceland temperatures 

lucky you =)
share with us your stats when it's running !

[zvisha]

Disconnecting the PSU's power will reset the SP30s knowledge of the PSU's limit, and will cause this algorithm to start again. If you change the cooling conditions for your SP30, you should power cycle your PSUs so the SP30 learns its new limits.

I didn't explain myself correctly in mails:
In order to cause recalibration, go to "settings" tab and set high PSU limit (1370W is over the top for 95% of PSUs).
It will take it down again to it's possible maximum over the next day.


Note that the hash rate is more expensive the higher you raise the watts.
You can get ~4TH for 2300W, but the next 600W will only provide 0.5Th - much more 'expensive' hash-rate in terms of power.
So I guess for 2500 the system will give about 4.2TH. If you pay 0.15$ per kWT, you still better running 4.5TH (100$ more). If you pay over 0.35c per kWT, you better run 4.2TH.



Regarding the source code of miner-gate - everything we do is open-source, but playing with code voids the warranty:

git clone https://github.com/Spondoolies-Tech/spond1
cd spond1
make get # downoads dependencies
make init # applying patches, build minimalistic kernel and buildroot
make build # builds everything
make deploy # assembles the rootfs and builds the full kernel

You don't need to build the full image, you can only build packages/spilib/miner_gate and then scp binary to /etc/bin/miner_gate_arm.

[edgar]

Feel free to browse his post history. though if i were he i would be deleting like a madman right about now.


i asked about shipped order numbers as it appears there are less than a handful in the wild.

and im also interested in factual details of the 'compensation package'.

I have not deleted any of my posts and I will not do it. I do take responsibility for what I have said in the past. Can't say the same thing about you since you would delete your posts.

As for the shipping queue if you are not a customer SP-Tech isn't obligated to present you the shipping report daily, same for the compensation package too. There are only a handful in the wild because there were just a few July orders and my July order was shipped in July and until now nobody complained about any delays. August orders will be shipped in August. Since it's just the 3rd day of the month I don't see how can there be tons of units in the wild. Since the compensation package will be offered in October for me as a customer finding the details now or in 2 weeks or in 4 weeks it's exactly the same since whatever I will receive will be in October.

Dunno … maybe RoadStress got an early one ? I remember him crowing a chapter or two back about expecting his first one with Collider.

My unit arrived today in Iceland. I hope to have it hashing online tomorrow if not then it will be online Tuesday for sure.

....and if you/we/i/they ARE customers? 


only when i err or go too far do i feel the need to delete /edit my posts but i was unaware this was a tit-for-tat event...

again, nobody has 'complained of delays' nor asked for a 'queue' or 'exact dates for exact orders', merely how many units have been shipped.

so far it seems 4.

also nobody other than you has mentioned 'tons' in the wild.. in fact no-one has said much of anything other than you and sadly its mostly been based in egotistical aggressive marketing fantasy.

why do we have to go round and round??

[jtoomim]

Note that the hash rate is more expensive the higher you raise the watts.
You can get ~4TH for 2300W, but the next 600W will only provide 0.5Th - much more 'expensive' hash-rate in terms of power.
So I guess for 2500 the system will give about 4.2TH. If you pay 0.15$ per kWT, you still better running 4.5TH (100$ more). If you pay over 0.35c per kWT, you better run 4.2TH.

About $0.022/kWh here, once we get above 200 kW of usage. About $0.04/kWh before that. The SP30's efficiency doesn't enter into my configuration decision calculus yet. Risk of broken equipment does, but the chance of improving the performance of all 68 of our machines with some simple mods largely offsets that.

git clone https://github.com/Spondoolies-Tech/spond1

Thanks! I'll take a look.

Zvi, I'm expecting significant diurnal variations in ambient temperatures in our datacenter. Does minergate take ambient/intake temperature into account at all for determining optimal settings?

Perhaps it would be good to add an adjustable ambient temperature coefficient for some of the major variables, like the PSU power limit. If the thermal shutdown temperature for the PSU is 150°C (what is it actually? I have no idea), and ambient is 20°C, that would be a temperature gradient of 130°C for the PSU's waste heat to flow over. For the sake of easy calculations, let's say the PSU goes into thermal shutdown if you use settings that result in more than 130 W of waste heat being generated in the PSU. That would indicate that the PSU has a thermal resistance to ambient air of 1 W/°C. If you then dropped the ambient air down to 5°C, you would expect to hit thermal shutdown at 145 W instead; if ambient rose to 35°C, then you'd hit shutdown at 115 W. As I understand the limit finding algorithm, you'd end up running your PSU at settings which work in the worst-case scenario (115 W) even during the best-case scenario (145 W) if you saw high-amplitude temperature fluctuations.

Another option might be to first learn what settings work at one ambient temperature, then after that process has completed, create a few separate learning context variable sets (structs or whatever) for different temperature bins, using the original ambient temp settings as a template, and refine the new bins independently. This would probably be significantly harder than simple temperature coefficients.

[Guy Corem]

We have unscheduled maintenance in our DC. It will take few hours at least until the machines will come online again.
We'll compensate for the down time.

Regards,
Guy

[Biffa]

We have unscheduled maintenance in our DC. It will take few hours at least until the machines will come online again.
We'll compensate for the down time.

Regards,
Guy

Was just about to email, which would really be too many emails from me in any one week

[Kuma]

Yep, thanks for notification, I was also writing an email  .

[Collider]

It is normal in the first day.
Let's see how it settles down. Should stop restarting.

The quoted stats are from the second day of mining.

The unit was in fact online more than 24hours before the "yesterday" stats were recorded.

Here are the detailed stats:



Mining on p2pool. (above)



Mining on normal pool (the one the sp10 from previously was connected to aswell).

[Biodom]

It is normal in the first day.
Let's see how it settles down. Should stop restarting.

The quoted stats are from the second day of mining.

The unit was in fact online more than 24hours before the stats were recorded.

Here are the detailed stats:

http://i58.tinypic.com/f5c1vt.png

Mining on p2pool. (above)

http://i60.tinypic.com/72akoi.png

Mining on normal pool (the one the sp10 from previously was connected to aswell).

Is the number in blue (4.5) the actual numerical value?
it is difficult to ascertain anything from the charts apart that they are probably somewhat in the vicinity of what they are supposed to be, looking closer to 4 than 4.5.

[Collider]

Strangly the unit seems to have been more stable on p2pool than on a regular pool.

The 24h average for the first pic was right around 4450 to 4500

The second one was around 4200 to 4450.

I am not complaining about the recieved hashrate, I was just trying to give Zvi some idea of the unit performance.
What the data seems to suggest is that the unit became less stable after the first 24 hour mining period. (which seems counterintuitive)

[zvisha]

Strangly the unit seems to have been more stable on p2pool than on a regular pool.

The 24h average for the first pic was right around 4450 to 4500

The second one was around 4200 to 4450.

I am not complaining about the recieved hashrate, I was just trying to give Zvi some idea of the unit performance.
What the data seems to suggest is that the unit became less stable after the first 24 hour mining period. (which seems counterintuitive)

This graph clearly shows severall downtime periods in both sp10 and sp30. I am not sure it is miners fault, espessialy since we see that pool has effect and i dont see such downtimes in my test units. I would like some more client information on this issue. Collider, Please send me data from you minepeon pages (asics, settings and main) durring a long run.

[Epoch]

"relevant questions being asked" - I think I answer all technical questions, please repeat your question if I missed it.

Let me ask one: if a July/August SP30 is expected to sustain 4.5TH/s on 240V, what sustained hashrate can I expect from the same device when powered from dual 120V/20A circuits instead?

[bbxx]

4.1 th, according to feedback from this thread

[crazyates]

Come winter, it gets very cold here in the north east, and it's very easy to keep ambient temps of our little (read: 150sqft) farming room down under 10C, even with 20kW of Antminers. Can we expect more than 4.5TH/s if we're on 220V, and with extremely low ambient temps?

[crazyates]

This particular SP30 shows in its stats log that it was hashing at a solid 4.5 TH/s for 24 hours on the 29th of July (burn in testing in Israel), so this is just a firmware+120V issue. Once I get this on 200V+, I expect I'll be able to get it back up to 4.5 TH/s or maybe even higher with some tweaking (and 254V?).

Does it make a loud screeching sound as Sp-10 does or is it making a whooshing sound? I understand that it is ~65-67dB at 1m, correct?

Yeah, 65db is a bit loud for home use, but I don't care for data center use.

If the SP10 and SP30 have about the same noise levels, I'd imagine the SP30 would be a bit less of a whine. SP10 has 6x 40mm fans, plus one PSU fan. SP30 has 4x 80mm fans, plus two PSU fans. I would expect the case fans will be a little less whiney, but the PSU will obv be more noise.

[opentoe]

Spondoolie-Tech didn't "have" to make the SP30 a pre-order. They could have made the product, like what other companies do, get an inventory, have solid specs and a working product, then sell it normally. It is the manufactures decision to use your pre-order money for R&D and making the product, but you'll never really know what you will end up with since it hasn't been made yet. ALL bitcoin manufacturers have the miners, "by the balls" in this industry now. Buying an expensive bitcoin mining rig(s) are worse then buying a car. At least you can sell the car at a later time for something.