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

Perftester exploration #206

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Perftester exploration #206

wants to merge 2 commits into from

Conversation

jussisaurio
Copy link
Collaborator

commit ac4d19954a8837717e18101851a849c8685c7764 (HEAD -> perftester-exploration, origin/perftester-exploration)
Author: Jussi Saurio <[email protected]>
Date:   Sun Oct 1 20:32:19 2023 +0300

    Server-connection: sort folded events in order of serial number
    
    This way, at the very least, the client's local board's serial
    number is always at least as high as the highest serial number in
    any incoming event, and doesn't ever decrease.

commit cedf13a0629a369fe83c2f93ac3cf32e07b72646
Author: Jussi Saurio <[email protected]>
Date:   Sun Oct 1 20:28:00 2023 +0300

    Perf-tester: add perf testers that type into notes
    
    - Use BoardStore() for perf-testers for a more realistic
      simulation of users sending events via the UI: the events
      are queued, folded etc. as normal.
    - Running perf tests with this setup yielded a big number of
      'Serial skip' warnings in the UI. After an investigation, I've
      simply added a note about not being able to guarantee sequentiality
      of events when folding is used on server-sent actions.

- Use BoardStore() for perf-testers for a more realistic
  simulation of users sending events via the UI: the events
  are queued, folded etc. as normal.
- Running perf tests with this setup yielded a big number of
  'Serial skip' warnings in the UI. After an investigation, I've
  simply added a note about not being able to guarantee sequentiality
  of events when folding is used on server-sent actions.
This way, at the very least, the client's local board's serial
number is always at least as high as the highest serial number in
any incoming event, and doesn't ever decrease.
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

Successfully merging this pull request may close these issues.

1 participant