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

Think about performance #34

Closed
RenCloud opened this issue Jul 9, 2019 · 3 comments
Closed

Think about performance #34

RenCloud opened this issue Jul 9, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@RenCloud
Copy link
Owner

RenCloud commented Jul 9, 2019

Some of the values are updated with higher frequency and some not, but to update the data at the moment the whole object is refreshed.

Think about ideas to get a better performance and deliver high update frequency of the changing values like speed, temperature etc. and a lower of the rest.

May with two shared memory's or some other Technics

@RenCloud
Copy link
Owner Author

RenCloud commented Aug 8, 2019

as addition to #39 there is a new value called sdk active

at begin only get memory map of the first byte to check if it is active
until it is load the whole file in two views? i think thats the best way
so forget two memory files only two views that should be better

or better

3 views one for active, one for fast, one for slow update values?

however close the / do not update the rest if sdk going inactive again

@RenCloud
Copy link
Owner Author

RenCloud commented Aug 8, 2019

double or so update rate when game paused?

@RenCloud RenCloud mentioned this issue Jun 22, 2021
18 tasks
@RenCloud
Copy link
Owner Author

Performance related to shared memory. Will be deprecated with V.1.12. May a new for that needs to be created than.

@RenCloud RenCloud removed this from the V. 1.11.x (update c++/pre Linux) milestone Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant