[MAINTENANCE] Explore FIXS TrafficLayer DLL/shared memory for VISSIM performance #99
Description
Task Summary
Explore FIXS TrafficLayer DLL or shared memory approach to resolve VISSIM driver model delayed response issue.
Why is this needed?
Current VISSIM driver model implementation has delayed response issues that impact co-simulation performance. Moving to a DLL-based TrafficLayer or shared memory communication could reduce latency.
Scope of Work
- Investigate root cause of delayed response in current socket-based communication
- Explore TrafficLayer as DLL alternative (in-process communication with VISSIM)
- Investigate shared memory IPC for lower latency
- Prototype and benchmark different approaches
- Compare performance vs current TCP socket implementation
- Document findings and recommend architecture changes
Environment (if version-specific)
- VISSIM version: 2022
- C++ compiler/version: Visual Studio 2019
Risks or Dependencies
- May require architectural changes to TrafficLayer
- DLL approach might need TrafficLayer to be compiled as both executable and library
- Shared memory approach requires synchronization mechanism design
Additional Context (optional)
- Related to performance issue [BUG] FIXS running slower than real time in co-simulation btw IPG and SUMO #88: FIXS running slower than real time in co-simulation
- Current architecture uses TCP sockets with TrafficLayer as central hub
- VISSIM integration via driver model DLL: ProprietaryFiles/VISSIMserver
- TrafficLayer entry point: TrafficLayer/TrafficLayer/mainTrafficLayer.cpp