Leave a reply

Synology – Network Speed Test

In the last weeks I searched for a ways to analyse the speed test of my Demo-Synology and to get clear answers how fast a client can maximum be with the 10Gbit connection.

The Hardware is following:
DS1821+ (CPU AMD Ryzen V1500B)
32 GB RAM
System: DSM 6.2.3-25426 Update 3
8x Seagate Exos X16
Synology Cache SSD 2x 400GB Read and Write
10Gbit RJ45 Card
RAID – SHR1

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

AmorphousDiskMark MTU 9000-9000

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

(Source for this help LINK)

Then you get following protocol that shows you the speed without the overhead of a protocol (SMB, NFS …) With the option „-r“ you can refer the test between server and client.

Connecting to host 172.16.100.20, port 5201
[ 4] local 172.16.100.10 port 50489 connected to 172.16.100.20 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 1.16 GBytes 9.93 Gbits/sec
[ 4] 1.00-2.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 2.00-3.00 sec 1.15 GBytes 9.89 Gbits/sec
[ 4] 3.00-4.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 4.00-5.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 5.00-6.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 6.00-7.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 7.00-8.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 8.00-9.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 9.00-10.00 sec 1.15 GBytes 9.90 Gbits/sec

[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec sender
[ 4] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec receiver


Good help for iperf is from JamesCoyle

Results in detail

Server MTU 9000 – Client 1500

Connecting to host 172.16.100.20, port 5201
[ 4] local 172.16.100.10 port 50485 connected to 172.16.100.20 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 467 MBytes 3.92 Gbits/sec
[ 4] 1.00-2.00 sec 723 MBytes 6.07 Gbits/sec
[ 4] 2.00-3.00 sec 882 MBytes 7.40 Gbits/sec
[ 4] 3.00-4.00 sec 718 MBytes 6.02 Gbits/sec
[ 4] 4.00-5.00 sec 911 MBytes 7.64 Gbits/sec
[ 4] 5.00-6.00 sec 883 MBytes 7.41 Gbits/sec
[ 4] 6.00-7.00 sec 868 MBytes 7.28 Gbits/sec
[ 4] 7.00-8.00 sec 817 MBytes 6.86 Gbits/sec
[ 4] 8.00-9.00 sec 932 MBytes 7.81 Gbits/sec
[ 4] 9.00-10.00 sec 512 MBytes 4.30 Gbits/sec


[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 7.53 GBytes 6.47 Gbits/sec sender
[ 4] 0.00-10.00 sec 7.53 GBytes 6.47 Gbits/sec receiver

AmorphousDiskMark Server MTU 9000 – Client 1500
AJA Server MTU 9000 – Client 1500


Server MTU 9000 – Client 9000

Connecting to host 172.16.100.20, port 5201
[ 4] local 172.16.100.10 port 50489 connected to 172.16.100.20 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 1.16 GBytes 9.93 Gbits/sec
[ 4] 1.00-2.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 2.00-3.00 sec 1.15 GBytes 9.89 Gbits/sec
[ 4] 3.00-4.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 4.00-5.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 5.00-6.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 6.00-7.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 7.00-8.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 8.00-9.00 sec 1.15 GBytes 9.90 Gbits/sec
[ 4] 9.00-10.00 sec 1.15 GBytes 9.90 Gbits/sec


[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec sender
[ 4] 0.00-10.00 sec 11.5 GBytes 9.90 Gbits/sec receiver

AmorphousDiskMark Server MTU 9000 – Client 9000
AJA Server MTU 9000 – Client 9000

Server MTU 1500 – Client 1500

Connecting to host 172.16.100.20, port 5201
[ 4] local 172.16.100.10 port 50495 connected to 172.16.100.20 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 1.06 GBytes 9.09 Gbits/sec
[ 4] 1.00-2.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 4] 2.00-3.00 sec 1.09 GBytes 9.36 Gbits/sec
[ 4] 3.00-4.00 sec 1.09 GBytes 9.34 Gbits/sec
[ 4] 4.00-5.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 4] 5.00-6.00 sec 1.09 GBytes 9.38 Gbits/sec
[ 4] 6.00-7.00 sec 1.09 GBytes 9.35 Gbits/sec
[ 4] 7.00-8.00 sec 1.09 GBytes 9.38 Gbits/sec
[ 4] 8.00-9.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 4] 9.00-10.00 sec 1.09 GBytes 9.41 Gbits/sec


[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 10.9 GBytes 9.35 Gbits/sec sender
[ 4] 0.00-10.00 sec 10.9 GBytes 9.35 Gbits/sec receiver

AmorphousDiskMark Server MTU 1500 – Client 1500
AJA Server MTU 1500 – Client 1500

Special Thanks to Tools at Work, first point of contact for system integration in Vienna Austria.


Leave a reply

Mac – not verified developer

In the last days I wanted to install LR/Mogrify 2 in my Lightroom Setup on my Big Sur MacBookPro. After the installation of the Plugin I got following error:

“magick” cannot be opened because the developer cannot be verified.

macOS cannot verify that this app is free from malware

and after this I got this message.

Failed to run Mogrify aborting export

You can fix it by open the Security Settings in your System Preference Panel and click on „Allow Anyway“

Security & Privacy

Leave a reply

AXLE MAM – proxy workflow

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

Where to buy AXLE in Austria: Tools at Work


Leave a reply

DayOwl – Network

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.

You can use this online tool to calculate your Host Address Range.
http://www.subnet-calculator.com

My home network uses following:
IP Address: 10.104.0.0
Subnet Mask: 255.255.240.0
Host Address Range: 10.104.0.1 – 10.104.15.254

The first 255 Addresses are reserved for administrativ devices:
IP Range: 10.104.0.0 – 10.104.1.0

Network Hardware (1-19)
10.104.0.1 – 10.104.0.19

in this range I use following rules:
Firewall (1-4)
10.104.0.1 – 10.104.0.4
Switches (5-15)
10.104.0.5 – 10.104.0.15
Internal Servers (20-40)
10.104.0.20 – 10.104.0.40
Printers (70-79)
10.104.0.70 – 10.104.0.79
Access Points (80-110)
10.104.0.80 – 10.104.0.110

I love when the DHCP Server is doing an IP-Mac binding and gives the fix IP-Addresses. But I would recommend to give the essential heart of you network manual fix IP-Addresses (switches and firewall).



Leave a reply

auto-convert to h265

My NAS has a lot of old privat video files and I want to convert them to the new h265-codec to save a lot of space. First thing to say is that you need a lot of CPU Power to process the video transcoding. Plan is to create a script that search the folder structure and then convert the file, remove the old (mov or mp4 file) and replace it with the new h265 encoded file.

After some research I got to following:
with help of Marcel in this post and Thomas Böhm

CPU rendering

find * -type f \( -iname \*.mp4 -o -iname \*.mov \) -exec ffmpeg -i {} -vcodec libx265 -crf 18 -vtag hvc1 temp_{} \; -exec mv temp_{} {} \;

If you just convert one file you use following command:

ffmpeg -i <path_to_orignal_file> -c:v libx265 -vtag hvc1 -crf 18 <path_to_output_file>

You can change the setting -crf to optimise you output files bitrate
If you want to know more about it visit Werner Robitza Homepage LINK

Apple T2 Chip – faster transcoding

If you use an Apple Mac Device with an T2 Chip (most OS devices after 2018) you can speed up the conversation a lot by using the hevc_videotoolbox of ffmpeg. This will increase the speed more than 30 times, compared to CPU rendering. BUT the quality is getting really bad. I would recommend to use the classical CPU rendering.

ffmpeg -i <path_to_orignal_file> -vcodec hevc_videotoolbox -vtag hvc1 -crf 18 <path_to_output_file>

After some testing and playing around I created following script. The logging is in englisch and german mixed, sorry for that.

You need to install ffmpeg and exiftool (this will help copy the metadata of the original video file to the new created one, so you do not lose the creation date). On a Mac you can use Homebrew to install the packages.

First install Homebrew:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

then ffmpeg:

brew install ffmpeg

and now exiftool:

brew install exiftool

Now you can create a new shell script and copy the content into your empty file. Move the file to the folder which you want to transcode (take care the it will automatically do it recursive). Then you have to change the last line in the script to the folder path you have stored the script. Now you can start the transcoding with

chmod + x <your-script-name>
#and then
./<your-script-name>
#!/bin/zsh
# this script can help you to convert files in folders and subfolder to h265 files (using CPU rendering, you can change the ffmpeg parameters if you need)
# copy the script to the folder you want to convert files, and change the path in the last lines of the script
# you need ti have ffmpeg and exiftool installed. On the mac you can use Homebrew

mkdir ~/Documents/log

machwas() {
    wo_bin_ich=$( pwd )
    echo $date "bearbeite Ordner ${wo_bin_ich}/ -------" >> ~/Documents/log/H265_transcoding.log
    SAVEIFS=$IFS
    IFS=$(echo -en "\n\b")
    for f in *; do
        # fuer alle Ordner
        if [ -d "$f" ]; then
            echo $date "habe Ordner $f erkannt" >> ~/Documents/log/H265_transcoding.log
            (cd -- "$f" && machwas)
        fi
                if [ $(find $f -type f -maxdepth 0 -iname "*.mp4" -o -iname "*.mov"| wc -l) -gt 0 ]
                  then
                    echo $date $f 'is mov or mp4' >> ~/Documents/log/H265_transcoding.log
                    if mdls -name kMDItemCodecs $f | grep -q "HEVC"
                      then
                        echo $date $f 'is HEVC' >> ~/Documents/log/H265_transcoding.log
                      else
                        echo $date $f 'is not HEVC, starting to prozess the files ATTENTION' >> ~/Documents/log/H265_transcoding.log
  #                      echo $f
                        name=$(basename "$f")
  #                      echo $name
                        ffmpeg -i $f -vcodec libx265 -crf 18 -vtag hvc1 /tmp/$name >> ~/Documents/log/H265_transcoding.log
                        exiftool -tagsFromFile $f -api largefilesupport=1 -extractEmbedded -all:all -FileModifyDate -overwrite_original /tmp/$name >> ~/Documents/log/H265_transcoding.log
                        mv /tmp/$name $f
                      fi
                  else
                    echo $date $f ' this is not an video file of the type mp4 or mov' >> ~/Documents/log/H265_transcoding.log
                  fi
    done
}
    IFS=$SAVEIFS

# Aufruf des Ganzen
cd  /Users/admin/Movies
machwas

Maybe I will get time in the next weeks to change the language to english and optimize the workflow.


Durch die weitere Nutzung der Seite stimmst du der Verwendung von Cookies zu. Weitere Informationen

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.

Schließen