750 karma · joined September 11, 2015
Meanwhile my 40GB X25-M runs flawlessly after 10+ years of 24/7 operation.
These newer drives probably have very advanced error correction systems that will hide defects for long enough that you get comfortable. Redundancy saves you from catastrophe, but not from the depression that follows the realization that everything is crap.
You need to look at perf./watt and complexity of use instead.
Something like this can replace 90% of databases: http://root.rupy.se
When the whole database is 2000 lines of code you don't need a manual?
NM: https://twitter.com/gregnacu/status/1632080241316225027
What about restore?
The real question is what is needed for these to be dim-able?
It messes with my head, and is fundamentally discouranging.
Also I cannot distribute that compiler for legal reasons, so I need to add another compiler to my project delaying it many months.
Linux has other problems, like 32-bit vs. 64-bit.
It seems to me we're in a vortex of complexity that we will never escape, fundamentally fueled by peak lithography.
Seriously considering going back to the C64.
Erlang is single threaded unless you copy memory between threads.
The only step left for Java to implement (after io_uring file stuff) is user-space networking.
The 256GB I mentioned was industrial server memories built to last.
If I wanted to get a little more performance per watt I would probably rewrite it in C with arrays of atomic variables.
But you need a VM with GC to be able to be productive during the day and sleep at night, so probably not...
https://blogs.oracle.com/javamagazine/post/java-loom-virtual...
As mentioned elsewhere in this thread, 100Mb/s, vs 1Gb/s vs 10Gb/s makes a lot of difference. IMO 1Gb/s is the only reasonable speed for home hosting as to saturate 10Gb/s you would need at least 20x (50Ah) lead-acid batteries of backup and that is almost industrial levels of investment/maintenance.
The final constraint is that disks and RAM uses more energy than you would think, 256GB DDR5 uses 80W! And they wear faster than you would think too at these nm! Be careful with writes!
So you need to plan your structure with the proper redundancy without going to far above the previously mentioned 1Gb/s saturation for your particular applications.
This in practice means you have to use Array of 64 byte Structure for your shared data.
Lua is not going to change that. You can hot-deploy C with a .so/.dll without losing performance.
You cannot have a live service that is interrupted by database modifications.
My solution is to use JSON.
But the most important feature to add is HTTP as transport and async-to-async (both client and server needs to only use a thread when they are doing work, zero idling): To scale a distributed database across continents:
2000 line distributed DB: http://root.rupy.se
"TeaVM is an ahead-of-time compiler for Java bytecode that emits JavaScript and WebAssembly that runs in a browser."
Windows 10 writes 100KB/s constantly.
That should be illegal.
OR ----
SoA is a necessary evil for multiple devs.: That way you let everyone free, but they are 100% responsible; and if they face plant completely you can replace a part entirely.
The trick is how to architect the structure: Replicate all services on all machines; they all call localhost; that way discovery is immediate and you can scale easy and read faults are both contained and tolerated. Write faults are never easy, so just accept them, nothing is perfect.
2 big hurdles to achieve that:
- Your entire solution needs to be completely async., end-to-end = non-blocking on all servers and clients, even deployment.
- Your data needs to be at the edges with relations to everything everywhere and unformatted = No SQL tables to alter.
----Which you pick depends on your situation. In some ways you can think of these as before and after your kids move out.
F.ex. Maven and Gradle and not necessarily better than Ant.
Older things are often stabler unless they are over-engineered.
Spring Boot is however completely meaningless in the first place.
LCD but persistent (if nothing changes very low power) and with colors (limited is ok, pebble time had 64) and higher frame-rates.
Contrast was suffering on those displays compared to the pebble 2 ones, but maybe there is something better now?
So to define a admin you just add a GROUP_NAME node called "ADMIN" to a user, pretty simple but not very fun when you need to find all admins.
It's the first and last admin interface I will ever do, since then I just hot deploy my hardcoded changes or edit the raw data instead.
To be able to remove the admin in Mastodon we would need to change laws since nobody would host a server that they cannot delete illegal content from.
Thinking about these things opens doors to understanding the absurdity of our current society.
In the end: to think that you can control anything is an illusion of energy abundance, and since we are running out of coal, oil and gas; my intuition tells me authority is going to dwindle slowly, then fast and finally all at once.
Thus, my conclusion is: don't build admin interfaces. :D
Adding to this the source-available economy that is the last step in our modern stack, needs user generated/hosted/owned content. So I think moderation tools needs to be less energy intense than manual.
My only solution so far is pride/shame, like hn; so you attach a pseudonym to things: after all that is how communities have worked since we started naming people.
This is incredibly hard to do, and nearly impossible to scale, but we need to go there.
In the short term one can look at Mastodon, which decentralizes the authority. It's messy but it sort of works.
I hope not, and then if I'm right and the GPU is more powerful than the Raspberry 4 one this board will run at 6W or something and then a stick-on heatsink wont do it...
Look at my link to the full copper one if I'm right:
http://www.enzotech.com/cnb_s1l.htm
I received it now and it's great (if it fits) well worth the expensive price!
For longevity 60C is better. I'm talking multiple decades at constant permanent full blast here.
You will need a heatsink on the Visionfive if the GPU does what I hope it does.
The Raspberry 4 GPU is only 1W vs. 5W on the Jetson Nano!
I'm hoping for a 2-3W GPU on the Visionfive and then you'll need a heatsink for MMO gameplay no question about it.
Longevity is now crucial as hardware peaks, heat kills electronics slowly but oh so surely!
Edit: Do you have a URL for those 3.xW and 4.4W claims... Then I think we wont see 100+ but cache can still be larger so you can have 100 at 1080p and that is enough for mainsteam adoption and replacing all other computers (Switch, PS4, XBOX, phones and pads etc.)!
The future belong to those that compile!
Not going to debate the gflops/w yet, but Raspberry 4 cores are also around 1W each and they kick ass compared to even M1 (much worse OFC, but per $/openess they still win imo)
BUT the GPU is apparently better which would make this THE SBC.
I will test my 3D MMO engine and give exactly what is what once I receive mine, should be a couple of days.
The Raspberry GPU has a serious cache problem, it can't render a triangle at 60FPS in 1080p!!!
But 100 non-instanced animated characters (each with a unique weapon in hand) at 60FPS and low res (800x600).
Jetson (1/2 Nintendo Switch GPU) does 300 at 60 FPS in 1080p.
If the Visionfive 2 is either:
- 100+ at 60 FPS and 1080p
- 200+ at 60 FPS and 800x600
I'm going ALL IN on Risc-V (my own VM for scripting the engine) and StarFive (buy a few to use as demo for the MMO instead of Raspberry 4/Jetson Nano).Just go here and buy one instead: https://www.waveshare.com/visionfive2.htm?sku=23875