- Jul 28, 2019
Today, yes... near future, maybe every apple desktop/laptop including high performance and flow-on maybe servers too ... need to re-think with future in mind. What Data Center manager wouldn't want lower power consumption/cooling requirement and options for higher density with existing facilities?The primary audience for ARM is mobile
Considering you responded faster than I could edit the post, I highly doubt you read my post carefully.Today, yes... near future, maybe every apple desktop/laptop facilities?
Single thread performance (high IPC+High clockspeed) on ARM is not-that-great, this makes it not-very-suitable for most high-performance use-casesincluding high performance and flow-on maybe servers too ...
The Data Center Manager that has customers that have high IPC+Clockspeed requirements. As I explained servers are selected on peak load, not average load. With ARM you hit the peak-performance-per-core earlier than X86_64. BY DESIGN.What Data Center manager wouldn't want lower power consumption/cooling requirement and options for higher density with existing facilities?
Consider it dropped (by me at least), following this response.Can we please drop this topic??
I freely admit to regularly jumping to conclusions and not reading posts in full before responding, but in this case even after re-reading your (edited) post carefully, I still have another opinion.Considering you responded faster than I could edit the post, I highly doubt you read my post carefully.
I am in no way suggesting immediate or even complete replacement of Intel architecture with ARM in Data Centers.I would not consider an ARM processor at this time.
My respect for actually admitting to it. You offense taken at all. I was more amazed, because you mostly don't make that mistake ;)I freely admit to regularly jumping to conclusions and not reading posts in full before responding, but in this case even after re-reading your (edited) post carefully, I still have another opinion.
I regret conveying (unintentionally) any sign of disrespect as you clearly spent time formulating your opinion and articulating it in the post.
Its not a BETA, but a NIGHTLY. Internally, we call its a "Technology Preview". Its a foundation for development and testing as new features get added and bugs get fixed. Because its based on TrueNAS 12.0 and OpenZFS it is more stable than usual, but we don't recommend anyone store their only copy of data on this. However, we really do appreciate feedback from everyone that does test and report issues.I was surprised to see Kris mention some kind of downloadable beta in the next few months for Scale, this really surprised me - is that actually true, anyone know?
Now I don't expect we'll see lots of ARM storage servers larger than 5 HDDs in the near future, but ARM is now at the #1 position of the TOP 500 list. Now maybe this isn't because of single core performances, but from it's new design: probably because it sets more in between CPU-based and GPU-based super computer design and very high performance interconnect makes it all come together. It's also more like a SOC for example it has memory on-die.Why ARM isn't magically going to be X86_64-grade
You seem to think ARM could magicallybe MUCH more performant. Newsflash: IT WONT.
SCALE provides docker CLI and API. Using these you can deploy Rancher and Kubernetes.I just spun up Truenas SCALE in a VM, with 8 vdisks for a pool, and was able to successfully launch a docker container with a dataset mapped through for config storage. I could access the container webUI at the forwarded port and everything looks to be running correctly.
I have a question about the SCALE clustering implementation though. At the moment I am using Rancher and RKE to deploy kubernetes nodes and manage the pods on each node. In unRAID, the docker UI is essentially an XML template for a docker run command. Containers deployed by docker compose or another method do show up, but lack the usual configuration features (logically). Will the kubernetes support be through a solution similar to RKE (where kubernetes runs within docker containers) or will kubernetes be deployed directly on the system? Also, is the idea that the docker or clustering UI will (also) be used to manage a kubernetes cluster and delegate node roles? My idea was to possible use FreeNAS as the base OS for a kubernetes cluster and built in management feature similar to Rancher would make that very appealing.