• Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
  • Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI005S – Triton 0.5 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using Helios2 with the Point Cloud Library for Dimensioning
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
    • Product Change Notifications (PCN)
  • Knowledge Base
  • Contact Support
  • Log In
home/Knowledge Base/Camera Setup/Testing the streaming performance of a system with four Triton color cameras

Testing the streaming performance of a system with four Triton color cameras

139 views 0 July 7, 2025 Updated on August 7, 2025

Summary

This knowledge base summarizes the results of performance tests on four TRI050S color cameras.

In the test, the four cameras were connected to a nominal-specification PC via a 4-port network interface card (NIC). The primary objective was to assess the cameras’ ability to maintain stable video streams to console while the host system was under significant computational load. The CPU usage was monitored during the test, and the system was stressed using IntelBurn. Even under the second-highest stress setting in IntelBurn, all four camera streams remained stable in both tests with no frame drops observed. When idle (no stress testing), CPU utilization remained at about 3%.

This testing scenario simulates use cases where cameras are expected to perform consistently in environments with limited computing resources or during periods of high system demand.

Setup

Cameras tested

  • Models: 4 × TRI050S-CC
    • Serial Numbers: 240604017, 240302125, 234600016, 234600018
    • Firmware Version: v1.127.0.0

Arena SDK version

  • Arena SDK 1.0.49.3

Host system

The nominal-spec PC was used as the host machine for these tests.

CPUIntel® Core™ i7-700 CPU @ 3.60GHz
GPUNVIDIA GeForce GTX 1050 Ti
MemoryTotal RAM18 GB
Committed5.1/18.2 GB
Cached8.8 GB
Speed2400 MHz
Slots used3 of 4
Form FactorDIMM
Hardware reserved142 MB
Operating SystemWindows 10 Pro
Disk SpaceLocal Disk (C drive): 110 GB
System FirmwareDriver Version 10.0.19041.1
Network Interface Card4-port Realtek PCLe 2.5Gbe Family Controller
Network Adapter SettingsMTU9014 Bytes
Receive Buffers512
Transmit Buffers4096
Speed DuplexAuto Negotiate
Interrupt ModerationEnabled/Adaptive
IPv4 Checksum OffloadRx & Tx Enabled
Energy-Efficient EthernetDisabled

Node values

NodeValue
AcquisitionMode
Continuous
ExposureAutoOff
ExposureTime500.0
StreamBufferHandlingModebufferHandlingMode
TriggerModeOff
PacketSize9000
GevSCPD80
DeviceLinkThroughputReserve10
StreamPacketResendEnableTrue
GevGVSPExtendedIDModeOn

Other test details

Test featureDetails
Power sourcePoE
CablesM12 to RJ45 IP67 Cat6a Cable – 2m, Amphenol
Monitoring toolsBasic system performance monitor (CPU usage only)
CPUID DWMonitor
Streaming targetConsole
Stress toolIntelBurn
  • IntelBurn details: Tests were conducted up to the second-highest stress level. The highest stress level was not executed due to computer hardware constraints unrelated to camera performance.
  • Test conditions: Only the CPU performance monitor and camera streaming processes were running during testing to ensure results reflected conditions without background interference.

Figure 1: Four Triton cameras connected to a Realtek controller.

Figure 2: Hardware monitor for Triton test: Voltage, temperatures, and fan speeds before the stress test.

Figure 3. Hardware monitor for Triton test: Voltage, current, power, temperatures, fan speeds, and clock speeds before the stress test.

Results

The test results are shown below:

  • CPU usage increased significantly during each level of the IntelBurn stress test, as expected. The test successfully loaded the CPU without errors or instability.
  • No frame drops were observed in any of the four TRI050S0 camera streams during any phase of the test.
  • The system remained responsive enough to maintain continuous console logging, even as it approached 100% CPU load thresholds.

Figure 4: Very-high-stress test with 4 Triton streams active; 100% CPU utilization; no frames dropped.

Figure 5. Completed IntelBurn test on host computer for Triton test with stress level of “Very High”.

Discussion

This test assessed whether four TRI050S cameras could maintain stable console streams on a low-spec PC under significant CPU stress. The results exceeded expectations. In each test, all four camera streams remained stable with no observable frame drops even at the second-highest IntelBurn stress level. Based on the results, it’s likely the system used was more powerful than necessary, and an even lower-spec PC could potentially deliver the same results.

Conclusion

Testing showed that four TRI050S cameras can each stream reliably with no frame drops on a low-spec PC, even under high CPU stress. These results exceeded expectations.

Was this helpful?

Yes  No
Related Articles
  • Projecting a Helios2 3D image to and from a 2D image
  • Focusing a Triton2 EVS Camera
  • Controlling Triton2 EVS camera’s event rate when connected at less than 2.5GigE (Event Rate Control / ERC)
  • Using Multiple RDMA Cameras on a Switch
  • Configuring RDMA for Linux
  • Configuring RDMA for Windows

Didn't find your answer? Contact Us

  Projecting a Helios2 3D image to and from a 2D image

© 2024 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}
Welcome to LUCID

We use cookies to facilitate online purchases and analyze our traffic. By clicking "Accept", you consent to our use of cookies.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}