SDK 20x performance loss between 1.22 and 1.29

astromatto

Hi,

I came back to my custom drivers for ZWO cameras and I sadly discovered that the latest SDK 1.29 (at least on Linux which is where I develop) has a disappointing performance loss compared to what I used to develop until today (1.22).
Not sure if is relevant, but I am linking statically to libAsiCamera2.a

What I am doing is pretty easy, I am retrieving the control value through the function ASIGetControlValue.

for my 533 which has I believe 16 caps it was taking a little bit less than 30 micro seconds on 1.22, when I bumped the SDK to 1.29 and linked my program to it, I am seeing times of 600+ microseconds to do the same operation, which is really bad.

If I switch back to 1.22, times go back to 30 microseconds.

Can you check why the performance got so bad?

My machine spec:
Linux 6.2.13 x64
Ryzen 7 5700x

astromatto

to add real numbers, I made a test program that can be easily replicated (it's worse than I reported originally, for that API the performance is worse by 1 order of magnitude)

The program looks for all available caps and tries to fetch them 50 times and gives back the average time needed to fetch all of them

1.22

~/data/repos/asi-rs (1.22) » cargo run --release --bin test_camera                                                                                                                                                                           matt@arcturus
   Compiling asi-rs v0.1.0 (/home/matt/data/repos/asi-rs)
    Finished release [optimized] target(s) in 0.34s
     Running `target/release/test_camera`
Found 1 camera(s)
Probing camera 0
Found: 16 controls for camera 0
Run average: 504.00ns

1.29

~/data/repos/asi-rs (1.29) » cargo run --release --bin test_camera                                                                                                                                                                           matt@arcturus
   Compiling asi-rs v0.1.0 (/home/matt/data/repos/asi-rs)
    Finished release [optimized] target(s) in 0.38s
     Running `target/release/test_camera`
Found 1 camera(s)
Probing camera 0
Found: 17 controls for camera 0
Run average: 622.80µs

astromatto

for aarch64 it seems the performance loss is about 60%

~/asi-rs (1.22) » cargo run --release --bin test_camera
   Compiling libasi-sys v0.1.0 (/home/astronaut/asi-rs/libasi-sys)
   Compiling libasi v0.1.0 (/home/astronaut/asi-rs/libasi)
   Compiling asi-rs v0.1.0 (/home/astronaut/asi-rs)
    Finished release [optimized] target(s) in 5.09s
     Running `target/release/test_camera`
Found 1 camera(s)
Probing camera 0
Found: 10 controls for camera 0
Run average: 1.96ms

~/asi-rs (1.29) » cargo run --release --bin test_camera
    Finished release [optimized] target(s) in 0.12s
     Running `target/release/test_camera`
Found 1 camera(s)
Probing camera 0
Found: 11 controls for camera 0
Run average: 2.67ms

w7ay

astromatto the performance loss is about 60%

Just a thought...

I notice that the newer SDKs found found 1 extra control than the newer ones.

Is it possible to time the averages by ignoring the newer control? That single one could be eating up a lot of time, and skewed the averages when you compared them.

Chen

Software@ZWO

Thank you for your feedback. We will take a test