10 ms·
> Today we are launching a developer preview of the new F1 instance. In addition to building applications and services for your own use, you will be able to pac
by wyldfire 10y ago
> Today we are launching a developer preview of the new F1 instance. In addition to building applications and services for your own use, you will be able to package them up for sale and reuse in AWS Marketplace.
Wow. An app store for FPGA IPs and the infrastructure to enable anyone to use it. That's really cool.
- perlgeek 10y agoI guess this will be a game changer for FPGA-mineable digital currencies. Maybe not for Bitcoin, because people have invested heavily into dedicated mining hardware, but I'm interested to see what it'll do for the smaller altcoins.
- mi100hael 10y ago> Maybe not for Bitcoin, because people have invested heavily into dedicated mining hardware The thing is, it seems like people always invest heavily into dedicated hardware when using FPGAs. I'll be interested to see what people actually end up using this service for.
- wmf 10y agoFor any cryptocurrency that's profitably mineable on AWS the difficulty immediately increases to the point that it's no longer profitable.
- tener 10y agoPerhaps not for the entire time, but bear in mind that the prices of cryptocurrencies fluctuate and you can spin up the VMs when it is profitable and shut them down when it isn't.
- nkkar 10y agoWould this mean that the currency would never fluctuate below that price point?
- ktta 10y agonot if you have a free-fall dump going on. This happens when investors lose hope in the long term future
- ThrustVectoring 10y agoIt's a price ceiling, not a floor. If prices go up high enough, it's worth turning on EC2 instances and paying for them with the mined cryptocurrency until prices fall. There's some wiggle room above the break-even point, since there is some delay between turning on miners receiving USD, and the miner has to eat that risk.
- nkkar 10y agoAh, yes, that makes sense, thank you!
- cookiecaper 10y agoYes, this IMO is the biggest flaw in bitcoin's design. It makes miners impossible to commoditize. As soon as a new ASIC becomes widely available, it defeats itself and becomes useless at the next difficulty increase. Consumer ASICs stopped being a thing for this reason. Now we have mega-secret custom hardware that can't be shared without destroying the investment put into their development. I don't think Satoshi's intention was that only a handful of massive investors with their own proprietary chipsets would be able to mine, but that's the natural consequence of the difficulty mechanism, and it really undermines bitcoin's core principle of decentralization.
- baybal2 10y ago>Wow. An app store for FPGA IPs I see people making video transcoder instances on day 1, and MPEGLA bankrupting Amazoners with lawsuits on day 2
- toomuchtodo 10y agoI guess the online distribution of FPGA configurations was an eventual event?
- alfalfasprout 10y agoThis was already a thing. Plenty of marketplaces exist for FPGA IPs. It's just not that well known because high end FGPAs run $7k+ and complex IP cores can be $20k+ for a license.
- problems 10y agoSo if you were to get a cheap license via a service like this, do you get access to the VHDL or equivalent or could you extract it in some way?
- baybal2 10y agothere are "encrypted" hdls, but encrypted no more than dvd discs. Find a right irc channel and ask for keys
- alexforencich 10y agoProbably not. Depends on how the core is distributed. Either you'll get HDL or netlists, and they may or may not be encrypted. Obviously the synthesis software has to decrypt it to use it, so like all defective by design DRM it doesn't make it impossible to get at the code, it just makes it more difficult. However, a netlist is just a schematic, so you would have to 'decompile' that back to HDL (and lose the names, comments, etc) if you want to modify it. It's also possible that you would only get the binary FPGA configuration file (this marketplace seems like one more for complete appliances and not IP cores) so you would have to back a netlist out of that somehow and then reverse-engineer it from there.
- ChargingWookie 10y agoYeah this is incredible for fpga users. There is now a market for freelance fpga developers
- CalChris 10y agoYes this is cool if you're already using FPGAs and yeah, there will be a market for FPGA designers. But I also think this is FPGAs for the Rest of Us. Suddenly, FPGAs are available without having to buy some development board from Xilinx, install a toolchain, use said (shitty) toolchain ... Me, I was thinking of FPGAs as being something I'd use down the road a few years, eventually, etc. But instead, I'm looking at this right now. This morning. Waiting for the damn 404 to go away on: https://github.com/aws/aws-fpga https://github.com/aws/aws-fpga This reduces the barrier to entry. It also reduces the transaction cost (h/t Ronald Coase).
- wyldfire 10y ago> install a toolchain, use said (shitty) toolchain ... Did I miss some details? Don't you still need those shitty toolchains to do design/simulation before you'd deploy it?
- CalChris 10y agoDeploy? No. With the F1 instance, I can sell it without said toolchains. I need them to develop but not to deploy. Edit: This isn't magic. This is availability. FPGA development remains hard.
- aseipp 10y agoIt's not that simple, I think. FPGA development is extremely labor intensive, both in design and especially in verification and testing. Large scale designs increase both the time needed for synthesis, verification labor, and testing, by a lot. If you don't have extremely large scale or resource intensive designs, this probably isn't for you anyway. Making the FPGAs more readily available is good for a lot of reasons, and opens the market to some new stuff, but it doesn't necessarily dramatically change the true costs of actually developing the designs in the first place. Basically, you're not going to deploy fabric live to your customers without having extensively tested it on your real world, production hardware setup, even if it's just a separate lab with identical hardware. That's going to be going on throughout the entire development lifecycle, and for anything remotely complex you can expect that to be a long process. You're going to be using that F1 server a lot for the development, so you have to factor in that cost. If you're a solo/small place you can probably amortize it somewhat thanks to The Cloud, however (reserved instances, on demand batching, etc).