Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking performance issues for clients #11

Open
ajgdls opened this issue Nov 2, 2022 · 1 comment
Open

Tracking performance issues for clients #11

ajgdls opened this issue Nov 2, 2022 · 1 comment
Assignees

Comments

@ajgdls
Copy link
Owner

ajgdls commented Nov 2, 2022

Links to the issue raised on each of the client repositories

DiamondLightSource/aioca#30
pyepics/pyepics#240
caproto/caproto#802
epics-base/p4p#94
epics-base/pvaPy#78
DiamondLightSource/cothread#33

@ajgdls ajgdls self-assigned this Nov 2, 2022
@mdavidsaver
Copy link

wrt. PVA clients, I think it would be a good idea to explicitly give the same pvRequest for both, including subscription queueSize. eg. record[queueSize=4]field() or record[queueSize=10]field(value,alarm,timeStamp) or something.

self._subscriptions.append(self._ctxt.monitor(pv_name, cb))

with p4p, pass request='...' to monitor().

fyi. If not provided, P4P defaults to 'field()', which selects all fields, and the server default queueSize. For QSRV, this is 4.

c.startMonitor("field(value,alarm,timeStamp)")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants