|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
05 Sep 2024, Jack Carlton, Forum, Python frontend rate limitations?
|
05 Sep 2024, Ben Smith, Forum, Python frontend rate limitations?
|
05 Sep 2024, Stefan Ritt, Forum, Python frontend rate limitations?
|
06 Sep 2024, Jack Carlton, Forum, Python frontend rate limitations?
|
11 Sep 2024, Konstantin Olchanski, Forum, Python frontend rate limitations?
|
27 Sep 2024, Ben Smith, Forum, Python frontend rate limitations?
|
11 Sep 2024, Konstantin Olchanski, Forum, Python frontend rate limitations?
|
11 Sep 2024, Konstantin Olchanski, Forum, Python frontend rate limitations?
|
|
Message ID: 2825
Entry time: 05 Sep 2024
Reply to this: 2826
2831
|
Author: |
Jack Carlton |
Topic: |
Forum |
Subject: |
Python frontend rate limitations? |
|
|
I'm trying to get a sense of the rate limitations of a python frontend. I
understand this will vary from system to system.
I adapted two frontends from the example templates, one in C++ and one in python.
Both simply fill a midas bank with a fixed length array of zeros at a given polled
rate. However, the C++ frontend is about 100 times faster in both data and event
rates. This seems slow, even for an interpreted language like python. Furthermore,
I can effectively increase the maximum rate by concurrently running a second
python frontend (this is not the case for the C++ frontend). In short, there is
some limitation with using python here unrelated to hardware.
In my case, poll_func appears to be called at 100Hz at best. What limits the rate
that poll_func is called in a python frontend? Is there a more appropriate
solution for increasing the python frontend data/event rate than simply launching
more frontends?
I've attached my C++ and python frontend files for reference.
Thanks,
Jack |
|
|