-
Notifications
You must be signed in to change notification settings - Fork 240
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
100% accurate classification of target host triples (i.e. linux-unknown-aarch64-musl
)
#756
Conversation
For ReferenceAll 115 patterns of classifiable terms for OS, Arch, Vendor, Libc, Channel, and Extension:
All 659 target host triple permutations, for reference: (that's across 26,470 installable bundles, after discarding 6,500+ non-build / anomalous files / packages)
|
8b1ba9c
to
e18526e
Compare
0f951de
to
ac72c9a
Compare
050ca21
to
8c38f3c
Compare
8c38f3c
to
f7574a3
Compare
Update
Canonical Arches25 distinct architectures
Canonical OSes13 distinct OSes
Canonical Libcs5 distinct libcs
PermunationsDown to 85 distinct permutations:
|
f7574a3
to
d272974
Compare
d272974
to
24c158f
Compare
86060aa
to
eadbbc9
Compare
e0446d1
to
82b643b
Compare
82b643b
to
7f86e7d
Compare
02cab21
to
7bb8040
Compare
6e3eb1d
to
51ede48
Compare
c70dfe8
to
fff0829
Compare
fff0829
to
8e62e12
Compare
This is a "Trust me bro" PR. There are too many changes to test them all exhaustively, but I've tested as exhaustively as I can - especially with the
lint-xyz
files - and it's been in prod where 1 bug and 1 backwards-compat issue have been discovered.Any other issues will just have to be fixed.
Summary 🚀
https://next.webinstall.dev/ can reliably detect, classify, sort, and match all known user agent strings, build asset names, and version identifiers.
Tasks
In tandem with https://github.com/webinstall/webi-build-classifier.
ARM Notes
Notes
Re: #755, more particularly #755 (comment)
Matches
Processes with
Cache Fetch Time
The recorded times are from a 16-core instance. It was also tested on an M1 Max, which was a little faster (possibly due to single-thread time).
Somewhere around 2-cores and 20 simultaneous requests the speed seems to be more dependent on network response time than the test conditions.
1 request at a time
5 requests at a time
10 requests at a time
20 requests at a time
25 requests at a time (1-core)
25 requests at a time (2-core)
25 requests at a time (2x 1/2-core)
25 requests at a time (2x 1/4-core)
25 requests at a time (16-core)
100 requests at a time