I created this a few months ago then i remembered this server and decided to get serious feedback on this i'm pretty sure this is the fastest/most efficient drive ever created in minecraft (1.9 only)
https://youtu.be/n4EWRBeNGu0
(Sorry for the terrible video quality)
Not to be mean. But we don't really do comamnd block based stuff here. Jsut to let you know. (Also a few people here might like get mad so just a warning of what may happen)
(11-17-2015, 11:38 PM)Chibill Wrote: [ -> ]Not to be mean. But we don't really do comamnd block based stuff here. Jsut to let you know. (Also a few people here might like get mad so just a warning of what may happen)
Ok I figured sense it only uses the command block to store data "traditionally" rather than having them all send redstone blocks like a regular command block machine someone would be interested and I really just want to make sure that it is as efficient as I think it is
(11-17-2015, 11:50 PM)jtsfour Wrote: [ -> ] (11-17-2015, 11:38 PM)Chibill Wrote: [ -> ]Not to be mean. But we don't really do comamnd block based stuff here. Jsut to let you know. (Also a few people here might like get mad so just a warning of what may happen)
Ok I figured sense it only uses the command block to store data "traditionally" rather than having them all send redstone blocks like a regular command block machine someone would be interested and I really just want to make sure that it is as efficient as I think it is
People with really bad pcs should be interested in this because it is relatively lagless
It's compact, but a 5 tick read is quite slow, especially since you aren't factoring the address decoding time. Conventional redstone would have higher throughput, i.e. 5 bytes per second if timed properly, though obviously it would be less space efficient.
This would be very useful for external storage, but don't use that for your registers for the love of god xD
If you're going for a fast (~10 tick) CPU, you need to be able to cache your SSD unless there's some command block wizardry that removes busing completely.
(11-18-2015, 04:03 AM)MagicalGentleman Wrote: [ -> ]It's compact, but a 5 tick read is quite slow, especially since you aren't factoring the address decoding time. Conventional redstone would have higher throughput, i.e. 5 bytes per second if timed properly, though obviously it would be less space efficient.
This would be very useful for external storage, but don't use that for your registers for the love of god xD
If you're going for a fast (~10 tick) CPU, you need to be able to cache your SSD unless there's some command block wizardry that removes busing completely.
Actually it is 1 tick read but with lag and repeaters and the torch I am currently using it slows it down I could probably make it 5-10 bytes a second the bulkier it is the faster it is I just had an idea to make faster read but basically it is not the reading that is slow it is the speed to stop reading
please learn to grammar don't mash sentences together it gets really annoying I wish I could fix it