INSTRUNET FILE AND RAM BUFFER SIZE LIMITATIONS
REFERENCE > ADVANCED TECHNIQUES >

instruNet iNet32.dll ≥ v3.5.0.1 has the following file and ram buffer size limitations. To upgrade to the latest version, click here.

• Maximum Size of Binary Merge File
  When digitizing and spooling a "Binary Merge" file to disk (i.e. all channels in one binary file, 4 bytes per point), the maximum file size is limited by the amount of free space on your hard disk. For example, you could digitize 10 channels at 1ks/sec/ch for 30 days and create a 103GB file, provided you had 103GB free. This requires iNet32.dll ≥ v3.5.0.1. Older versions were limited to a 2GB maximum binary merge file size.
  
  
  103e9 = (4bytes/pt * 10ch * 1000s/sec/ch * 60sec/min * 60min/hr * 24hrs/day * 30days)
• Maximum Size of Non-Binary Merge File
  All disk files of type other than Binary Merge are limited to a maximum size of 2GB (2e9 bytes).
• Maximum RAM Buffer Size
  All ram buffers are limited to a maximum size of 2GB (2e9 bytes).
• Maximum Points-Per-Scan
  The maximum Points-per-Scan is 500M points. A "scan" is a RAM buffer used to contain one channel's data.
  
  
  500M points = 2e9 max-bytes-per-ram-buffer / 4 bytes-per-point
• Maximum Number-of-Scans
  The maximum number-of-scans is 2 billion (2e9).
• Maximum Points for entire digitization
  You can digitize virtually forever provided you do not overload your RAM or hard disk space. For example, you could digitize 100Ks/sec for 100 years with Points-Per-Scan set to 10e6 (40MB Ram buffer per channel) and Number-of-Scans set to 31e6.
  
  
  31e6 number-of-scans = ((60sec/min * 60min/hr * 24hrs/day * 365days/year * 100years) * 100e3samples/sec) / 10e6pts-per-scan.