Ryzen 7 9700x is #20 in single-thread performance.
13900 would be only two generations back, so not seeing anything 3-years-old, let alone mid-range, that is in the same performance group.
There.
Now we can get back to the TrueNAS beta discussion.
1 Like
Yeah, true. Still the 9700X is not anywhere near the best and only about 15% better than the arguably mid range 12600K which is more than 3 years old, and only in this synthetic bench.
The server uses ryzen 9700x, which is undoubtedly one of the best single-core performance CPU currently available.
I’m simply pointing out the absurdity of the claim, that was the point, and given that it is pertinent to SMB performance, it was a valid one.
Hi,
I read your announcement about REST API and I’m really disappointed.
May be websocket is better for browser but, as you surely know, REST API are not make for browser. They are usefull (and absolutely needed) for anyone want to automate remote managing of truenas.
For example I don’t use browser but a lot of command provided by scripts, awx, other service for IT4IT and many other stuff like that.
All of this disappears.
All the work (and I suppose it’s the same for a lot of Truenas’s users) I did in last year is rubbish now!!!
Are you jocking?
Im’ sure you know websocket was the old way of doing remote connection. REST API is the new way used by all software makers (opensource or licensed sw).
This decision have no sense.
Instead of work hardely on your REST API (because there some issue and some functions/call that need to be improved) you choose to follow an old style solution.
No words to comment this.
I hope you will change you decision…
REST was first introduced in 2000.
WebSocket was standardized in 2011.
REST is the old way and WebSocket is the new way.
Surely REST API is the most used way to manage remote services.
Do you understand the impact of doing this kind of choice?
Yep. REST is great for some things. For dynamic & asynchronous frontend/backend communication it is not. Websockets are the way to go for a system as dynamic as TrueNAS is today and our implementation follows a standard JSON-RPC on-wire specification.
Json RPC Spec:
https://www.jsonrpc.org/
Reference Python Client:
1 Like
I wonder if there is some confusion with “rpc” and “websocket”, if not also just the generic term socket communication.
Implementations of RPC and socket communication go back to at least the 70s and 80s respectively, but neither are really relevant with respect to the API changes and deprecation.
The idea of these forums is get that feedback. Please describe what you do, why you use the REST APIs and why change is difficult. Perhaps we can work out a solution??
2 Likes
Why is the instances page so barren when the UI design of the apps page could have just been re-used for this page since it works pretty well for quick glancing resource usage and status of the app/instance?
3 Likes
Hi, thank for you question.
Just a preamble before answering. I’m not interested in the history of websocket or REST API. I simply notice that all major vendors (Google, AWS; Oracle, IBM, Nutanix, VMware (vRealize) even Proxmox and many others) use and improve continously their REST API. Something would means.
In any case I pass last year to make hundred of code-lines using your REST API to provide automatic VM creation with TrueNAS Scale over a HyperVisor layer (Proxmox). This to have one storage env for each of my colleague so everyone have separate and dedicated resources (CPU,RAM, disk space) for their storage area.
In particular I provide a VM using proxmox REST API, after I customize the VM with TrueNas creating dedicated data pool with a dedicated user profile reachable by SFTP, SMB or webdav (this managing also K8S layer).
In last months I’m just solving some bugs and improving some functions but now I can provide a stable solution to manage all.
Just in 24.10 you changed to docker (and I was happy of this because docker seems more stable and usable) so I’m working to change all command related to webdav.
In practice I send automatically lots of commands from different source to proxmox and TrueNAS VMs.
I think even other guys are using in some way (more or less) your REST API for doing actions or create data protections or any other stuff they need.
Looking at your websocket solution it doesn’t seem so fine and simple to use like REST API. I need to change the prospective of what I’ve done e rewrite all from the beginning (even locate what are the source machine and how to send properly command).
I’m not an expert of websocket communication so I prefer to study more to understand how they works and how to use them. In any case is a rilevant effort I have to do to maintain my automation for next years.
Can you tell me in how much time you think REST API will be eliminated? Now is simply deprecated but do you think for this year or even next one REST API stil be there (and maintained)?
thank in advance
Again, experimental feature means it just hasn’t enabled all those knobs and visuals yet. In long run having them on two separate pages will make more sense, but we’ve still got plenty of work to do in fleshing them out before we get rid of the experimental Label this fall.
This is interesting. I remember you mentioned on the previous Tech Talk episode that, for example, you guys are trying to wait for a large proportion of users to upgrade to 25.04 before adding the app IP addresses to the app catalog (I could be getting the details wrong here). However, there could be a significant proportion of users (myself included) who might skip 25.04 because of the impact on VM’s. My plan is to try Fangtooth but if the VM migration doesn’t go well (already tried the beta without success - int() base 10 catastrophic failure), I will stay on 24.10 until 25.10 comes out in the fall.
1 Like
That June date is set to coincide with 25.04.2 release, which by then I would expect most, if not all blockers for folks migrating have been solved. (We are still at BETA1 right now)
Considering how rough the old VM section was, I’d expect this a pretty low-bar to reach, but we’ll see how it goes in the coming months.
As a fall back, folks still on 24.10.X will be able to remove / re-add the application post June 1st to get their IP functionality and updates back as well. Annoying, but you aren’t quite completely marooned on that release should you decide to stay on it.
1 Like
Ah, this make sense, thank you for clarifying!
I know I’m in the minority, but I never had any problems with the old VM section. Works great for my use case. I actually…like it 
TrueNAS Scale looks to be shaping up to be a good replacement to Core, I look forward to moving over to it with its many app hosting options with docker, VMs and Lxc.
Now all I need to do is find the time to test scale in anger on a spare Dell server I have, after I find the time to get some sort of rack cooling solution going. Present time scale suggests I may be going a long time on Core well past it’s use by date 
1 Like
Its a good question… we don’t have a definitive answer. It depends on customers and community feedback.
In general, new features and capabilities are implemented via the websocket interface only.
The WebUi will use the websocket interface for better real-time capabilities.
The REST APi will be used by third parties… we will support the transition to websockets.
What programming tools do you use for the REST API… help with that transition may be important.
Morgan
1 Like
A REST API to WebSocket gateway would be nice…
2 Likes
So… basically maintain the current REST API (which is a sort of wrapper around the websocket API)?
Hi,
All code is in python 3.11 and vsCode (IDE) on linux or windows systems.
I call REST API with library “requests”.
Regards