Skip to content

Performance issues from Exceptions #224

Open
@ShadowMarker789

Description

@ShadowMarker789

When dealing with large amounts of tags on shaky network conditions, raveling and unravelling the LibPlcTagException exceptions is drowning me in CPU overhead.

Is there a way to deal with these tags in an "exceptionless" context where we can just check whether the operation was successful or not using the Status of the tag instead of these exceptions?

Currently when the network goes down thousands of exceptions are being raised as we have thousands of tags we're monitoring.

When this happens the CLR proceeds to have a very bad time from the exceptions being raised and CPU usage spikes up uncontrollably.

I'd very much rather set a static boolean value to suppress exceptions being raised from Read, ReadAsync, Write, WriteAsync, Initialize and check the Status of the tag instead.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions