You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to test our compiler by uploading a query, running traffic, and measuring the result. But what does result mean in this case and how does the simulator provide facilities to retrieve these results?
The first and most simple type of result I can think of is that we want to retrieve data from the "storage" service. Typically this is done with a HTTP GET request. This means that this simulator must allow us to query individual services at the end of a run. Is this possible?
What are the other types of metrics that should be measured to test the compiler?
The text was updated successfully, but these errors were encountered:
* Start with a Github workflow
* permissions
* Update.
* Less mem.
* More fixes.
* Only two?
* Update compiler.
* Another compiler update.
* Is it ubuntu latest?
* Update tracing compiler with fixes.
* Update modules.
* Update test script.
* Fix.
* Typo.
* Split the workflows.
* permissions
* Checkout.
* More fixes.
* rmtree being obnoxious.
* More obnoxious things.
* typo.
* More testing madness.
* minor for macs.
* Typo fix.
* Final.
We want to test our compiler by uploading a query, running traffic, and measuring the result. But what does result mean in this case and how does the simulator provide facilities to retrieve these results?
The first and most simple type of result I can think of is that we want to retrieve data from the "storage" service. Typically this is done with a HTTP GET request. This means that this simulator must allow us to query individual services at the end of a run. Is this possible?
What are the other types of metrics that should be measured to test the compiler?
The text was updated successfully, but these errors were encountered: