-
Notifications
You must be signed in to change notification settings - Fork 160
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
Add an EpochSyncTime table #621
Comments
It is probably a good idea to add a |
erikd
added a commit
that referenced
this issue
May 31, 2021
This table is mainly for sync time performance validation. Different machines are likley to have different results in this table. Closes: #621
erikd
added a commit
that referenced
this issue
May 31, 2021
This table is mainly for sync time performance validation. Different machines are likley to have different results in this table. Closes: #621
erikd
added a commit
that referenced
this issue
May 31, 2021
This table is mainly for sync time performance validation. Different machines are likley to have different results in this table. Closes: #621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is mainly for measuring sync performance.
It would require a simple table like:
Basiically we need an
IORef
orTMVar
containing aMaybe UTCTime
. Ondb-sync
startup this mutable variable is set toNothing
. Then, on eachLedgerNewEpoch
event it retrieves the old value of the mutable variable and replaces it with the current time. If the old value isNothing
it writesNothing
to theseconds
field of the table above. If old value is notNothing
the time in the mutable variable is subtracted from the current time and tihe difference in seconds written to the database.One very minor gotcha that needs to be fixed first. Currently a
LedgerNewEpoch
event is generated erroniously ondb-sync
program start up. This would need to be suppressed for the above to give correct results.The text was updated successfully, but these errors were encountered: