Page tree
Skip to end of metadata
Go to start of metadata




Benchmark settings

  • Windows Drive Partition :GPT
    Windows format Block size : 64k (for Pyramix audio only) - Default 128k (for audio and video) - RAID level Block size: 64k
    Windows Drive Indexing and compression turned off 
  • Pyramix Playback buffer set Level 3 (default)
    Record Block size to 64k (default)
  • For high track count, Merging highly recommends to record in "single media" (all tracks in 1 single file) and not in "one file per track", especially for DXD and DSD.
    One file per track is more demanding than single media.
  • Real-time sampling rate conversion : DSD256 or DSD128 (DSDIFF) in a DXD project requires a lot of resources, therefore the number of I/Os may need to be reduced in such a mismatched format Record scenario (e.g. DSD256 in a DXD project)
  • For better performance disable the Waveform Generation while recording (Pyramix Settings > Playback/Record > Waveform to None or Generate AFTER recording)
  • DSD files are recorded in SDM D (default)

Drives

  • All drives are SATA III - 6Gb/s, plugged on SATA III - 6Gb/s ports
    HDD models : Western Digital Re serie or RED PRO serie.  (7200RPM - 128MB cache)
    SSD models : SSD Samsung 850 MZ serie or Crucial MX serie.
  • Do not use Green or Eco drives.
  • RAID hardware : Intel RAID (on board) or HighPoint RocketRAID 2720SGL

Notes

  • When more than 70% full, a HDD performances quickly decreases.  A SSD is not subject to that issue.
    HDD performances decreases depending on its fragmentation, it should be defragmented on a regular basis to sustain performance over time.
  • On the opposite, SSD should never be defragmented.
  • RAID arrays in "Initialize", "Degraded" and "Verify" state have their performances reduced.
  • RAID Array types:

RAID 0: min 2 - max 4 drives (striping - good performance - no redundancy)  
RAID 1: min 2 - max 4 drives (mirroring- low performance - redundancy)
RAID 10: min 4 drives (striping and mirroring- good performance - redundancy)
RAID 5: min 3 - recommended 4 drives (striping with parity - low performance - redundancy)
https://en.wikipedia.org/wiki/RAID 
http://www.raid-calculator.com/raid-types-reference.aspx

Maximum number of tracks table

"One file per track" track count displayed under brackets. 
One file per track is more demanding than single media, and not recommended when doing large track count.

PCM

HDDSSD

single
drive
RAID0
2 drives
RAID1
2 drives
RAID10
4 drives
RAID5
3 drives
single
drive
RAID0
2 drives
RAID0
4 drives
RAID1
2 drives
RAID10
4 drives
1Fs128(96)192(128)128 (96)192(128)96(64)256(256)384(384)384(384)256(256)384(384)
2Fs64(48)96(64)64 (48)96(64)48(32)128(128)192(192)192(192)128(128)192(192)
4Fs32(24)56(32)32 (24)56(32)24(16)64(64)96(96)96(96)64(64)96(96)


DSD

No Sampling rate conversion involved, files are recorded in their native formats; DXD files in DXD project and DSD 64/128/256 files in DSD64/128/256 project respectively.

"One file per track" track count displayed under brackets.  
One file per track is more demanding than single media, and not recommended when doing large track count.
DSF and WSD formats have limited track count (6 channels), therefore Merging recommends to record in DSDIFF or MTFF.



HDDSSD

single
drive
RAID0
2 drives
RAID1
2 drives
RAID10
4 drives
RAID5
3 drives
single
drive
RAID0
2 drives
RAID0
4 drives
RAID1
2 drives
RAID10
4 drives
DXD16(16)32(24)16(12)32(24)12(8)48(48)64(64)64(64)32(32)64(64)
DSD6416(16)32(24)16(12)32(24)12(8)48(48)64(64)64(64)32(32)56(48)
DSD12816(12)32(24)16(12)32(24)12(8)48(48)64(64)64(64)32(32)56(48)
DSD25616(12)32(24)16(12)32(24)12(8)48(48)64(64)64(64)32(32)56(48)



DSD in DXD project specific

DSD256 or DSD128 (DSDIFF) in a DXD project requires a lot of resources therefore the number of I/Os may need to be reduced in such a mismatched format Record scenario. 
Recording DXD using the Horus / Hapi A to D converters is very intensive in CPU processing with AD in DSD.
In such a scenario MassCore SMP license is mandatory for high track counts.
The processing needs to be balanced between Windows and MassCore CPUs  (For example with a 8 Core CPU, 5 Cores for Windows and 3 for MassCore or 4-4).
Windows OS must be properly configured as per Merging specifications and recommendations. 
CPU i7 (or above) and 16 Gb of RAM recommended.
SSD(s) required (recommended SSD Samsung 860 serie)
MassCore must be set to Low latency mode, with MassCore SMP key (Extended) for such track counts.

For better performance when recording, disable the Waveform Generation while recording (Pyramix Settings > Playback/Record > Waveform to None or Generate AFTER recording).
For editing, please be aware that edits such as Crossfades requires twice the processing resources, so track count may not to be reduced (or convert your medias to DXD during the editing work, and relink to the DSD256 medias for the final processing).



Project DXDProject DSD64Project DSD128Project DSD256
MEDIA
(single media)
Playback *
& Outputs
RecordPlayback *
& Outputs
RecordPlayback *
& Outputs
RecordPlayback *
& Outputs
Record
DXD64 Tracks
& Outputs
64 inputs





DSD6464 Tracks
& Outputs
64 inputs64 Tracks
& Outputs
64 inputs



DSD128

56 Tracks***
& Outputs

48 inputs

64 Tracks
& Outputs
64 inputs

DSD25648 Tracks***
& Outputs

48 inputs**






64 Tracks
& Outputs
64 inputs

*Projects have no tracks limitation, the specified playback track value is based on the tracks containing media.
**Requires optimal configuration (TurnKey) with MassCore SMP key (Extended). 
Benchmarks were performed with i7 CPU (i7-9700k-3.6GHz) NON HyperThreaded mode with 5 cores to MassCore and 3 cores to Windows repartition.
*** Playback track count without edits (such as crossfades).  When editing with crossfades, performance can reduce significantly and stalls may occur. 
We recommend not crossfading between the same media source, and if the performance cannot be sustained, to convert your medias to DXD during the editing work, and relink to the DSD256 medias for the final processing.





  • No labels