search

bowtie-json-schema / bowtie

JSON Schema in every programming language
https://bowtie.report/
Other
52 stars 40 forks source link

Collect timing information during runs #35

Open Julian opened 2 years ago

Julian commented 2 years ago

This is slightly tricky as we don't synchronously wait for responses, which may arrive in later messages read from the stream -- especially so if we move away from reading from implementations line-by-line.

But it'd be nice to time how long it takes to get responses back.

ashmit-coder commented 6 months ago

This is slightly tricky as we don't synchronously wait for responses, which may arrive in later messages read from the stream -- especially so if we move away from reading from implementations line-by-line.

But it'd be nice to time how long it takes to get responses back.

Hey julian sir I would also like to keep this as my potential project for gsoc 2024 along with bowtie-trend. ( If I am not mistaken and this issue falls under the bowtie-perf project). I would like to know more about this and how I may explore new things for this project including the qualification task. :)

Julian commented 6 months ago

The qualification task for this one is essentially the same as the other 2 Bowtie related ones -- simply grabbing a "good first issue" ticket and trying to work it through. Other info is in https://github.com/json-schema-org/community/issues/605 on how to start researching the tools specific to this issue, but I'll add some of that in to the description here as well.