mervincm

I had a CRS226 it was a great switch if you didnt want LACP channel bonding. Well still have it, its in a box now but .... a couple other points sfp+ fiber modules can be had for 20-30$, so they are not Super expensive either, plus 10-20 for the LC/LC fiber patch cable. Mikrotic has 75$ SFP+ modules that support N-baseT, so if you must use copper, you can do so at 2.5, 5.0, or 10 gbps Mikrotik has a 5 meter fiber cable with integrated sfp+ for less than 50$

work specifically to hardware transcode plex? this functionality is brand new, so it would have just started working.

I don't know why turbo modes are not supported, but there is quite a bit of chatter about it spread around this forum, and I have yet to find anyone getting it to work on the DSM config I use at least (6.2.2u3 w 1.04b and DS918+) The best web GUI I have found for performance data on a DSM system is netdata in a docker, but while there is PILES of interesting stuff in real time, precious little on CPU frequency.

I wonder what order these are listed in? if it is phys,phys,phys,virt,virt,virt,virt , maybe it is just a display issue? virtual HT CPUs can't run at a higher frequency than the core performing the work right? Even if it is Phys,virt,phys,virt etc. Is that even possible? I know individual cores can go UP from base to turbo, but can individual cores go DOWN from base to speedstep? I understood that was a CPU wide change? maybe this is all just cosmetic? Speaking of turbo, it lists your max, but your turbo is never used. That is ALOT of untapped CPU, expecially on an L CPU. PS this is why I use the i3s. no turbo

is there something you can point to better understand the load profiles? The speed is just CPU frequency, so that is simple to understand. BIOS support for this CPU was in there from the initial release. The systemboard is a gen newer than the CPU actually. I can play with the BIOS, but Windows tools like CPUz read it correctly (if that matters) My results are consistant, they just are not correct. Thank you!

Works fine for me on i3-8350K, 6.2.2U3

It seems to work as designed for me, if a bit more delayed than I expected. It correctly drops it to 800 MHz when it is completely idle, and up to full speed when it is really busy. It is not very often at the mid frequency (2400) but it is there on occasion, so it is working. thanks! PS I have not found a way to see an accurate frequency, it always says 4000MHz when it is in fact running at 4600MHz. It is OC from 4000 to 4600, and I believe the OC is functional based on my geekbench test values, they are too high for a stock speed i3-8350k, but about right ration for a 4600MHz version. It appears to just be a display issue.

excellent! thanks so much for your work. Once these show up at my local QNAP dealer I will buy one and see what it does for my DS1813+ !

I have a i3-8350K CPU, on z390 chipset, with jun 1.04b+DS918+DSM6.2.2-24922U3. My BIOS/CPU supports base frequency at 4.0GHz, power saving lower frequencies (speedstep) but it does not have turbo mode. It also supports overclocking. I have read here that (Jun 1.04b+DS918+DSM6.2.2-24922U3) is not able to correctly move from the base frequency to a lower one based on idleness. Is this script designed to help solve this issue? (seems YES, but just to confirm) Are you aware of a way to see in real time the frequency the CPU is running at in an xpenology system. geekbench can give you an idea of relative max performance, but not confirm lower idle frequencies.

Plex has just released a new version of plex media server with hardware transcoding support on linux with Intel 9th gen CPU. Before I buy one to upgrade my NAS, can anyone confirm functionality in Xpenology? Specifically - 918+ -6.2.X DSM -1.04b loader -Plex media server with plex pass and hw transcoding enabled -Intel 9th gen CPU with built in iGPI HD630, eg. i5-9600k

What an excellent idea! I wish synology would add this to base DSM for my real 1815+ !!!

While I am primarily a windows guy, I got rid of all my perminent windows servers when I started using xpenology. I occasionally have a linux server running as well, but my full time install is always the xpenology system. It just makes all those complications go away. I also own a real synology, but my xpenology system is so much faster and expandible that I have delegated to backup / redundancy related tasks.

If you are willing to buy a plex pass you can use hardware transcoding. hardware transcoding gives a much better over all experience, and while not perfect, it is still definately the way to go. assuming you have a plexpass -do not use a 9xxxx series CPU, they hw transcoding driver in xpenology will not support this CPU. The most recent series it supports is the 8xxx series. In my mind the perfect budget plex server CPU is the i3-8100 quad. for something with a bit more juice look for a i3-8350K (400Mhz faster.) ignore everything from there on up till you get to the 8700k. Why? because Xpenology does not support turbo boost. since your CPU will only ever run at its base frequency (or lower if power saving states are enabled) all these CPUs with middle range base frequency and good turbo frequency are basically a waste. The i3's are fine because they do not support turbo. The 8700K is fine becuase it have a high base frequency and 6 cores. use the 918+ xpenology build, I set my serial number, but don't bother with setting the MAC values. I just moved from a 4xxx haswell (like yours) to an i3-8100 to get a wider range of supported hardware transcoding. It does make a difference, but its not like the haswell support isnt still helpful.

Port multipliers will allow you to connect multiple HDD to each Sata port. That's not what you will be doing here. You are natively hooking a single HDD to each Sata port on these cards. as long as the chipset itself is supported, you will be fine.

I don't think most of the serial number/mac advice is required for plex hardware assisted transcoding. You likely need it for the bundled apps, but not for plex. Also, 100% CPU usage is not an issue with Plex. It will work hard, 100%, to transcode till the buffer is full, then it will drop and throttle. This is expected plex behaviour for software transcode.