telemetry-python
dud
| telemetry-python | dud | |
|---|---|---|
| 1 | 14 | |
| 3 | 166 | |
| - | - | |
| 2.6 | 6.0 | |
| 8 months ago | 15 days ago | |
| Python | Go | |
| Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telemetry-python
-
Data Version Control
VS Code, etc
> I think the challenge I have is that since you’re getting IP address that will be an opportunity to abuse.
Yes! And we are migrating to the new package / infrastructure because of this - https://github.com/iterative/telemetry-python (DVC's sister tool MLEM is already on it and it's not sending (saving) IP addresses, nor using GA or any other third-party tools, data is saved into BigQuery and eventually we'll make publicly accessible - https://mlem.ai/doc/user-guide/analytics to be fully GDPR compatible). It's a legacy system that DVC had in place. There was no intention to use those IP addresses in some way.
> I think perhaps the only other way would be to support an automated distro that doesn’t include it so users are at least able to easily choose a version.
Thanks. To some extent brew-like policy (not sending anything significant before there is a chance to disable it and there is clear explicit message) should be mitigating this, but I'll check if it works this way now and if it can be improved.
dud
-
Ask HN: How do your ML teams version datasets and models?
I've used DVC in the past and generally liked its approach. That said, I wholeheartedly agree that it's clunky. It does a lot of things implicitly, which can make it hard to reason about. It was also extremely slow for medium-sized dataset (low 10s of GBs).
In response, I created a command-line tool that addresses these issues[0]. To reduce the comparison to an analogy: Dud : DVC :: Flask : Django.
[0]: https://github.com/kevin-hanselman/dud
-
🐂 🌾 Oxen.ai - Blazing Fast Unstructured Data Version Control, built in Rust
There is also https://github.com/kevin-hanselman/dud
- Data Version Control
-
Tup – an instrumenting file-based build system
I very much agree with you about DVC's feature creep. The other issue I have with it is speed. DVC has left me scratching my head at its sluggishness many times. Because of these factors, I've been working on an alternative that focuses on simplicity and speed[0]. My tool is often five to ten times faster than DVC[1]. I'd love to hear what you think.
[0]: https://github.com/kevin-hanselman/dud
[1]: https://kevin-hanselman.github.io/dud/benchmarks/
-
Non-Obvious Docker Uses
I don't know about replacing Make with Docker, but I use the two together to good effect. One of my favorite hacks is adding a 'docker-%' rule in my Makefile to run make commands in a Docker image[1]. It's a bit mind-bending, and there's a few gotchas, but it works surprisingly well for simple rules.
[1]: https://github.com/kevin-hanselman/dud/blob/e98de8fcdf7ad564...
-
Git-annex – Managing large files with Git
Thanks for sharing your experience. It's non-trivial and surprising behavior like this that drove me to build a custom system[0] myself. When I started researching version control tools for large files, I remember feeling like git-annex and Git LFS were awkwardly bolted onto Git; Git simply wasn't designed for large files. Then I found DVC[1], and its approach rang true for me. However, after using DVC for a year or so, I grew tired of DVC's many puzzling behaviors (most of which are outlined in the README at [0]). In the end, I built the tool I wanted for the job -- one that is exceptionally simple and fast.
[0]: https://github.com/kevin-hanselman/dud
- Alternative to Git LFS or DVC
- Show HN: A small and simple alternative to Git LFS or DVC
- Dud: a lightweight tool for versioning data alongside source code and building data pipelines.
- Dud: a tool for versioning data alongside source code. A faster and simpler alternative to DVC.
What are some alternatives?
Estranged.Lfs - A Git LFS server implementation in C# designed to run in a serverless environment.
dvc - 🦉 ML Experiments and Data Management with Git
Mimic - We use the actual live data from the International Space Station to control a 3D-printed model that moves the solar arrays and radiators to track the real ISS in real time. We also host two pages that display ALL of the public ISS telemetry below::
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
rudolfs - A high-performance, caching Git LFS server with an AWS S3 and local storage back-end.
docker-merge - Docker images as git repositories, so you can merge them.
Task - A task runner / simpler Make alternative written in Go
oxen-release - Lightning fast data version control system for structured and unstructured machine learning datasets. We aim to make versioning datasets as easy as versioning code.
pachyderm - Data-Centric Pipelines and Data Versioning
Git - Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
ploomber - The fastest ⚡️ way to build data pipelines. Develop iteratively, deploy anywhere. ☁️
null - Nullable Go types that can be marshalled/unmarshalled to/from JSON.