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
Consider to add some extra information to runs. In order to be able to compare different os, web servers, databases, php versions... we should be able to grab, on each run, that information. Note it's information to be fetched from the server. That way we could compare performance between mysql and postgres, or php5.3 vs 5.5 or linux vs windows... or whatever. And the only way to do so is to know against which server each run was done. Right now we lack that completely. those new "variables" should not affect bases nor groupings... but perhaps should be searchable (in the form) and also readable (in the list of runs). Again, please fill a new issue for that.
The text was updated successfully, but these errors were encountered:
OS: 1-word (linux, windows, darwin...) + long description (something like uname and uname -a, for example).
Webserver: 1-word (apache, shit*ngnix....) + long description/version.
PHP: Version + run mode (module, cgi...)
RDBMS: 1-word (moodle driver used, for example) + server version.
Having them there (with some normalization) is the 1st step and we should be recording that asap. later can be decided how that information is shown/used.
Copied from #17 (comment):
Consider to add some extra information to runs. In order to be able to compare different os, web servers, databases, php versions... we should be able to grab, on each run, that information. Note it's information to be fetched from the server. That way we could compare performance between mysql and postgres, or php5.3 vs 5.5 or linux vs windows... or whatever. And the only way to do so is to know against which server each run was done. Right now we lack that completely. those new "variables" should not affect bases nor groupings... but perhaps should be searchable (in the form) and also readable (in the list of runs). Again, please fill a new issue for that.
The text was updated successfully, but these errors were encountered: