mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.4 2022-01-31T15:30:52Z 2022-01-31T15:30:52Z Nick Mathewson nickm@torproject.org 2022-01-31T15:30:52Z urn:sha1:01d99373089f8131d1df9758fce45ffaa3fbf659 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T15:53:06Z urn:sha1:30b3818a9e31b0ebe96d4a32aa9bceb16610f994 This commit puts the native-tls crate behind a feature. The feature is off-by-default in the tor-rtcompat crate, but can be enabled either from arti or arti-client. There is an included script that I used to test that tor-rtcompat could build and run its tests with all subsets of its features. Closes #300 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T13:40:35Z urn:sha1:6f29d485e460b30cba992bcb407bf3c7e2a479b7 This should help avoid some amount of temptation towards API proliferation. 2022-01-18T13:46:36Z eta tor@eta.st 2022-01-18T13:41:43Z urn:sha1:2aeac45f49f5266fe3cf3f9f249ed4eb8aeffabb We now conduct benchmark tests with multiple concurrent streams (by default; this is configurable by passing `-p` to `arti-bench`). Currently, these results just get "flattened" for the purposes of statistical analysis (as in, results_raw contains the results of each connection's timing summary, across all benchmark runs). This might be something we wish to change in future. The stats summary now also records "best" and "worst" values for each metric, to give a rough idea of the range of values encountered. Additionally, we now support writing the benchmark results out to a JSON file. A future commit may integrate this with CI, so that we have benchmark results for every commit as a build artefact. (some documentation was also fixed) part of arti#292 2022-01-14T15:00:11Z eta tor@eta.st 2022-01-13T16:23:11Z urn:sha1:82beb52fca8b973f7889210c6790867ed376eab4 We now do multiple samples (configurable; default 3) per type of `arti-bench` benchmark run, and take a mean and median average of all data collected, in order to hopefully be a bit more resilient to random outliers / variation. This uses some `futures::stream::Stream` hacks, which might result in more connections being made than required (and might impact the TTFB metrics somewhat, at least for downloading). Results now get collected into a `BenchmarkResults` struct per type of benchmark, which will be in turn placed into a `BenchmarkSummary` in a later commit; this will also add the ability to serialize the latter struct out to disk, for future reference. part of arti#292 2022-01-13T14:16:01Z daniel.eades danieleades@hotmail.com 2022-01-13T14:16:01Z urn:sha1:1ecf383e8f740e70c79f122ce10314cba9f7a6af 2022-01-11T14:40:32Z Nick Mathewson nickm@torproject.org 2022-01-11T14:40:32Z urn:sha1:7d3482ca1ae7249b73feeca98595bae5f4c6afe9 2022-01-11T14:37:45Z Nick Mathewson nickm@torproject.org 2022-01-11T14:37:45Z urn:sha1:c5f50b7d41f79895819bfdb78ee1bcd3d65ce17c 2022-01-10T13:44:53Z eta tor@eta.st 2022-01-10T13:44:53Z urn:sha1:e6e65d6574a8ee6c5fb17918e65893e76f7e9540 Minimize the required version for each dependency. Closes #275 See merge request tpo/core/arti!228 2022-01-08T21:36:49Z Neel Chauhan neel@neelc.org 2022-01-08T21:36:42Z urn:sha1:439b8b3e64f6f4cb5a032ee3ceafb4675003f259