Test Client: MacPro 2019 96 GB RAM System: BigSur 11.2 3,3 GHz 12-Core Intel Xeon W
1. Test – Difference between MTU Sizes
9000-1500 MTU If you mix the MTU size (Server 9000 and Client 1500) the network speed drops down to 7.53 GBytes / 6.47 Gbits/sec testet with iperf. And about 727 write and 700 read, tested with AJA System Test,
1500-1500 MTU If you use the same default MTU size (Server 1500 and Client 1500) the network speed looks good 10.9 GBytes / 9.35 Gbits/sec testet with iperf. And about 810 write and 785 read, tested with AJA System Test,
9000-9000 MTU If you use the same big MTU size (Server 9000 and Client 9000) the network speed looks good 11.5 GBytes / 9.90 Gbits/sec testet with iperf. And about 865 write and 1076 read, tested with AJA System Test,
Conclusion: If you use the same MTU the Network overhead is less and you get more performance. The best performance is with the MTU 9000
2. Test – AmorphousDiskMark
Searching for a tool do make standardized test I found AmorphousDiskMark from Katsura Shareware. It is a great tool and you can download it form the App Store – Download. It automatically creates 4 different Szenarios (Forum): SEQ1MQD8 – sequential read/write one big file multiple streams SEQ1MQD1 – sequential read/write one big file single streams RND4KQD64 – random read/write many small files multiple streams RND4KQD1 – random read/write many small files single streams
3. Test – AJA System Test
An easy way to test your storage is to use the AJA System Test. You can choose an Target Disk and specify the Test File Size. I would recommend to click on the charts icon on the bottom of the window to open the graphics with the frame number vs MB/secs. Here you can easy see if you get dropped frames or if the peak speed is very high but the average speed is weak.
4. Test – iPerf (Network Storages)
You have to make sure that you network connection to the storage is good and gives you the maximum speed. The easiest way to do this is, using iperf. It is an client – server application and you have to download and start it. You can download it at iperf.fr
The „server“ site can be startet with „iperf3 -s“ and on the client site you use „iperf3 -c <ip-address>“
On you Synology you can easily use it in a docker image by using this command: (Install Docker Package, Enable SSH in the System Settings and then type following)
sudo docker run -it --rm -p 5201:5201 networkstatic/iperf3 -s
You can import pregenerated proxy files into your AXLE media asset management system. This can speed up your workflow, when you do not generate the proxy files on the same machine where your MAM is installed.
First you have to set the „Existing Proxies“ path in the „Advanced“ settings. There you can set the „Location of Existing Proxies:“ to a folder which AXLE should observe.
You have to rename your pregenerated proxy files with the prefix „DC“ example: austria.mp4 -> DCaustria.mp4
Keep the same folder structure like your highres material. The you can move the proxy files itto the import folder. Important you have to create a parent folder with the same name like your catalogs name.
After this you can move the highres material to the AXLE catalog. Depending on the amount of data it should now start to sync the proxy files. Every successful imported file will get an „.done“ as prefix.
The technical specification of the proxy file are „mp4 file h.264 codec with aac audio codec downmixed stereo – The video is 1MB/s 480p“ according to AXLE Support
This guide should help you to set up networks with higher ranges and should set the default „ip-ranges“ for devices, like I do. It is thought for home networks and small business networks. In the last 10 years the numbers of Network Access Devices (NAD) has increased a lot. Even if you have one machine it can have different network interfaces and will require ip-adresses on all of them. So it can easy happen that your subnet with a /24 range is getting quite small after a few months. Changing this later makes you a lot of work, because you have to change the subnetmask on every device. Devices with enabled DHCP Client Service will not make you the problem, but static IP Adresses like switches, printers… will not be able to communicate with network devices out of their subnet. For example if you forget to change the subnet on a printer, you can use it from all devices which are in the network range of the subnet. But if you sent a printer job from a machine outside this subnet this will not work because the tcp connection can not be answered from the printer.
My solution is to create bigger networks from scratch on. I never use /24 subnets (with about 255 usable addresses). I also recommend to use A-Class Networks. Starting 10.X.X.X and then use something like the postal code or the door number to easier remember the range.
For example: Vienna – 4th district (ZIP-1040) is then 10.104.X.X Korneuburg – (ZIP-2100) is then 10.210.X.X
This will save you time with routing issues with you want to make site-to-site VPNs or even normal VPNs.
Die Cookie-Einstellungen auf dieser Website sind auf "Cookies zulassen" eingestellt, um das beste Surferlebnis zu ermöglichen. Wenn du diese Website ohne Änderung der Cookie-Einstellungen verwendest oder auf "Akzeptieren" klickst, erklärst du sich damit einverstanden.