I added some stuff there for you to delete/edit/play around with. Just a quick splurge so no worries it should not be kept, but may help with some ideas at this early stage of collecting thoughts.
I think weāre still on topic: the title says āMassive scale maidsafe farmā
What a great way to get there, by telling everyone about it
there = Massive scale maidsafe farm;
It would be sort of like a 51% attack, though closer to a 76% attack in the SAFE network. There would possibly be very minor data loss at something less than 76%, but not significant, I think.The difference being that a 51% attack would seek to gain some control, whereas the 76% attack would be purely distruptive, as no degree of control could be gained.
The main interest here to me would be to see how the network adapted to such a massive churn event. Iām guessing that it might slow the network some, but it should recover. Multiple such events in succession could mess things up, Iām guessing, but the neat thing is that the the network ANT workers would just keep on doing their simple tasks as presented to them, till it stablized. Then whatever the condition, it would move forward, loss or not.
Anyway, thatās just my non-developer takeaway from all Iāve been able to glean, but itās an interesting image.
As an interjection to this thread, I think it would be a good thing to note post 4 of this thread MaidSafe Korea: Updates and Questions - #3 by happybeing where David Irvine lays out his hopes regarding the distribution of the network and farming, especially as regards big rigs.
haha dont worry about that. Building a massive storage farm is a whole different game then running scrypt mining rigs in your basement
Iām still not convinced on how I would not get an unfair advantage over home farmers.
Peering in a datacenter will get me much lower responsetimes over average Joe with his 4 yr old crappy sweex nat router.
Iām not sure how maidsafe will handle this, but using thin provisioning on my backend storage server will also fool the network into thinking I have petabytes and petabytes of storage I donāt really have.
What might be even worse, if I can get this thing to compile on Solaris I can run 128 hardware threads + zoning to fire up thousands of maidsafe instances on a $1000 Sun T5240. All with the competitive advantage of being peered to a number of fast backbones.
(All this is just theoretical btw, not planning to make a setup like this, I think itās a better investment to just buy maidsafes and storjās and wait till the adult industry finds out about cheap storage)
Thatās performance advantage. Read the two posts @fergish kindly shared, which explains why it might not be to your financial advantage.
I think what I donāt understand yet is how the network might punish temporary farmers. Iām sure even with just the geeks, freaks and volunteers together the network will be enormous, but there has to be some kind of incentive for Joe to leave his computer up and running 24/7. I mean if I can plug a couple of usb hdās into my dd-wrt router Iād be fine with it, but to leave my computer on all the time (and without rebooting) I would need to earn some kind of incentive. (Especially windows users with the beloved āImportant updates have installed and your computer will reboot in 15 minutes whether you like it or notā will have a disadvantage).
Iām also not sure what happens to the maidsafe data on my drive when I have to reboot. Will there be a kind of hashing to see which data is still valid or will all just be gone (including reputation) ?
Power is expensive where I live. Running a simple, not too fancy computer 24/7 costs me 50 euroās per year.
Other regions will be cheaper but their internetconnection will probably suck compared to mine.
Apologies if this is all covered in the whitepaper, but unfortunately Iām not smart enough to understand half of it.
Depends on what you mean by ātemporary farmersā. You wonāt be penalized much if any for rebooting or other short-term offline conditions.
If you are online for a while and get data stored in your vault, then go offline for an extended period, your vault will be downranked and become less able to earn safecoin, while being always available and responsive will give your vault a higher ranking and earn you more safecoin.
The earning of safecoin IS the incentive to leave the computer on. My understanding of the vault software is that it will run at a low resource level. No reason to keep a monitor on while not in use, etc.
See Best Safe Node hardware for more data than you can probably use, but a pretty good coverage of some possibilities.
If your desktop is a powerhog, thatās another matter. Iām setting up a couple nodes that consist of low-power Intel Atom processors in netbook and thin client configurations that use very little energy. Others are using Odroid, or even raspberry pi. These can be gotten cheaply if you want to run a dedicated farmer with a low resource footprint.
If your desktop computer is what you want to use for only when you are online, or doing other things (image editing, gaming, web surfing, etc.) you can run a vault on it to access the SAFE network, and turn it off when youāre not using it. It just wonāt earn much safecoin in that instance. But maybe it will still earn some, even then.
Hope that helps.
It helps a bit, thank you
Still wondering if my $1000 128 hardware threaded sparc beast is cheaper then 100ās or 1000ās of raspberries or o-droids delivering similar performance⦠But I could never compete with integration in dd-wrt and/or open-wrt *HINT HINT DEAR DEVS ⦠The network could scale up to bizarre proportions in short time if their userbase decides to earn some coins and plug in a spare usb disk to their already running and paid for router.
The reason why I keep going on about this is because I see massive potential both for maidsafe and storj and Iām still trying to wrap my head around most of the concepts.
The one thing every IT manager worldwide has in common is that they wake up with storage costs nightmares 2-3 times a week and crying themselves to sleep again. The last place I worked at grew from 70 tb of managed storage to 700tb in just 3 years. Storage is a growth limiting factor nowadays because setting up reliable storage isnāt that easy. The price of a TB of enterprise grade storage can easily be $1000-$2000 per terabyte per year if you calculate the san switches, sfpās, support contracts, licences, downtime, cables, hbaās, people costs and so on and on⦠The need for storage grows way faster than the size of harddrives (I believe only 20% growth in size per year on average for enterprise class drives).
Now Iām not expecting to see for example netflix ditch amazon anytime soon. But some teenager somewhere will at some point code a competing delivery platform with just $100 investment. Nowadays youāre just out of luck if you need lots of data for your ideaā¦
Iāve said before, and David Irvine has agreed, that rigs such as yours will not hurt the network, and if they work economically for you then thereās no downside. It could even be very beneficial to the network. As long as enterprize participants are stable actors, theyāll benefit from the arrangement. They wonāt hoover up undue proportions of safecoin, however. Theyāll find that it is a good mutual relationship.
Hey @Erwin ⦠kickin up some dust and scouring the forum for participants looking at farming. Appears you had some monster rig in mind. Heads up fast forward 2 years to 2016 - check out the current state of affairs.
3 posts were merged into an existing topic: MaidSafe Dev Update ā October 4, 2016 ā TEST 10
Looking back a couple years the enthusiasm for farming seemed high. A simple strategy to re-engage old interest is efficient and effective. While it may remind some how long its been, it will also remind them how far its come. This can be applied to many other threads.
i plan on using my 8 core desktops. 4tb hgst drives that arent cheap but are very reliable, and some icybox 10 bay,usb 3, for overflow drives.
Slightly curious as to the effects of node rank when we look at large amounts of volatile memory and how the vaults handle the use of this memory rather than archiving information right away?
Overall would it be good to have a boatload of RAM and will it be used efficiently by vaults? Personally im considering running drives in RAID on a FTTH connection. If loads of RAM would help for caching on the network then il get a load of it alsoā¦
My understanding is from reading the info about caching is that each node will have upto a certain amount of cache. So I think its better to be running multiple nodes (vaults) so that you can maximise the amount of memory used for caching
@BIGbtc Sorry I stepped out for a while
Currently caught up in other things so I donāt really have the time to get a farm going. Also I started work at one of the largest san storage vendors in the world so I guess my boss wouldnāt appreciate my conflict of interests
Congrats- feeding the family always comes first
IMO this is not a conflict of interest as MS is not a storage company per se - in fact Maidsafe will compliment any san storage in the same way san storage compliments device/hardware storage. IMO mentioning Maidsafe to industry experts - which your boss is - would impress and enhance your standing, rather than threaten it.
Im not suggesting you risk your job for Maidsafe. Just offering a different perspective.
Good luck with your career.
Thanks
Maidsafe will have a long long road before we can expect enterprise adoption. The san stuff we sell is a multitude more expensive than a self built storage solution. Starts at around $10K for just a couple of terabytes of data, but our customers are more than happy to pay for it. They want boring, reliable, tested. Theyāre happy to throw money at aws because itās proven technology.
My previous employer even took it a step further. They wouldnāt touch anything that hadnāt been sold for a least a year with a 10 ft polestick. Theyād buy a couple of the new gerenation hp servers when they got out, and then whoever wanted to have a go at them was more than welcome to make things break.
From my perspective this job was kinda boring. Their conservative approach costed them extremely little downtime, and if things went down they had clearly documented disasterrecovery in place.Needless to say, but they werenāt fond of virtualization (except solaris zones), bladeservers, hyperconverged systems. Saved them tons of money.