You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to address performance issues encountered while sending frames using fuzzing within the ID range of 0x000 to 0x7FF, encompassing a total of 2048 different identifiers. I noticed that after sending the first 1000 frames, the program begins to slow down significantly. With a set interval of 10 ms, the program should send about 100 frames per second, but the rate drops to merely 10-20 frames. Performance only returns to normal after exceeding the 2048 frame mark.
Interestingly, a similar issue occurs when the ID range is set from 0x000 to 0x3FF (1024), with the slowdown resolving after surpassing 1024 received frames.
For testing, I am using the ESP32RET module and SavvyCan software version V213. It is worth noting that with the previous software version, V199, these problems did not occur. I am confident that the issue is not hardware-related, as I am using a computer equipped with an i7-11850H processor, 32GB of RAM, a Samsung 990 PRO SSD, and running Windows 11.
Has anyone else experienced similar issues or could suggest possible solutions?
Thank you in advance for any assistance.
The text was updated successfully, but these errors were encountered:
That sounds suspiciously like a bug in SavvyCAN but I'm not sure where/why right now. It's weird that it would happen like you're describing but your description is quite helpful for me to track this down. Are you sequentially scanning the address space in each instance?
I've noticed a problem that occurs both with sequential and random ID scanning. Regardless of the method, after reaching a specific number of IDs (2048), the rate of frames per second returns to normal.
I attempted to compile the application myself from the master branch to investigate the issue. Unfortunately, after successful compilation, the application shuts down when trying to launch fuzzing functions or send custom frames.
Do you know what could be causing this issue? I am using Qt version 6.6.3 and Qt Creator 13.0.0 for compilation. Is it necessary to use an older version of Qt, such as 5.14, to compile code from the master branch?
EDIT: The issue of compilation and launching is no longer a problem, as with the version of Qt 5.15 that we managed to download, the application compiles and launches without any issues. Now, we need to identify the cause of this bug.
I conducted a frame transmission speed test on a 2020 13” MacBook (i5, 16GB, OS Ventura). After initiating the test on MacOS, I noticed that within the ID range from 0x000 to 0x7FF, the frame transmission speed slows down. When the count exceeds 2048, the frame transmission rate per second does not increase as it does with the program running on Windows 10, and remains within the range of 5-30 frames per second. Below, I am also attaching screenshots.
Hi,
I would like to address performance issues encountered while sending frames using fuzzing within the ID range of 0x000 to 0x7FF, encompassing a total of 2048 different identifiers. I noticed that after sending the first 1000 frames, the program begins to slow down significantly. With a set interval of 10 ms, the program should send about 100 frames per second, but the rate drops to merely 10-20 frames. Performance only returns to normal after exceeding the 2048 frame mark.
Interestingly, a similar issue occurs when the ID range is set from 0x000 to 0x3FF (1024), with the slowdown resolving after surpassing 1024 received frames.
For testing, I am using the ESP32RET module and SavvyCan software version V213. It is worth noting that with the previous software version, V199, these problems did not occur. I am confident that the issue is not hardware-related, as I am using a computer equipped with an i7-11850H processor, 32GB of RAM, a Samsung 990 PRO SSD, and running Windows 11.
Has anyone else experienced similar issues or could suggest possible solutions?
Thank you in advance for any assistance.
The text was updated successfully, but these errors were encountered: