
Comet - Licensing only
Comet.ml Makes Experiment Tracking Effortless with Clear Dashboards
The biggest benefit is visibility and reduction of time spent manually.
Keeps ML experiments organized and comparable.
Clear Visibility Into Experiments, Metrics, and Model Performance
Powerful Experiment Tracking and ML Workflow Management
Comet.ml Makes ML Experiment Tracking and Visualization Effortless
Great for Beginner Developers Learning ML & LLMs, Though Some Gaps Remain
Experiment tracking has improved collaboration and simplifies comparing model iterations
What is our primary use case?
My main use case for Comet is ML experiment tracking and evaluation. A specific example of how I use Comet is that I typically track model runs, compare the metrics and the hyperparameters, and keep the experiments organized so I can easily see what worked and reproduce the better results.
What is most valuable?
What I find particularly useful about my main use case with Comet is having the experiment history, metrics, parameters, and the other runs details organized in one place.
The best features Comet offers in my opinion are the visual dashboards, the run comparison, and the experiment tracking in ML, and those features stand out for me because they automatically capture things such as parameters, code, metrics, and system information, making it much easier to understand and reproduce experiments.
Comet has positively impacted my organization by mainly improving collaboration and productivity by keeping the experiment results, the metrics, and the model comparisons in one place, making it much easier to share results with others and quickly identify which approach is performing better so we can iterate without spending as much time organizing experiments.
What needs improvement?
One area I would like to see Comet improve is in the ease of navigating and comparing a large number of experiments, as better filtering and quicker ways to find specific runs would make the workflow even smoother and save some manual effort.
The documentation part of Comet is generally very useful, but some advanced features could be explained more simply for new users, and I would also appreciate even smoother navigation and comparison when working with a large number of experiments.
I chose a rating of 8 out of 10 because Comet covers the core experiment tracking needs really well, especially tracking and comparing runs, and to make it a 10, I would mainly want smoother navigation for bigger projects and more intuitive guidance around some of the advanced features.
For how long have I used the solution?
I have been using Comet for around a year.
What do I think about the stability of the solution?
Comet's tracking and evaluation results are reliable and consistent with what I expect from my experiments, and having the metrics and run details recorded clearly also makes it easier to validate results rather than relying on assumptions.
Comet is stable and reliable during my usage, especially for logging metrics and tracking the experiments across different runs.
What do I think about the scalability of the solution?
I found Comet to be quite scalable for the projects I have worked on, including handling larger workloads without major issues, and as the number of experiments grown, the navigation can take a little more effort, but overall, it has handled my use case reliably.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before Comet.
What was our ROI?
I have seen a positive return on investment with Comet in my experiment management process, as it has definitely reduced the manual work and helped me iterate on models faster.
Which other solutions did I evaluate?
Before choosing Comet, I evaluated a few alternatives, mainly MLflow, and we ended up preferring Comet because its experiment comparison, visualization, and overall workflow felt more convenient for our use case.
What other advice do I have?
I appreciate the integrations with Comet because it fits into the ML tools I am already using rather than forcing a completely different workflow, and the collaboration features are also useful for sharing experiments and comparing results with teammates, especially when multiple people are working on model iterations.
I primarily use Comet as a cloud-based platform, accessed through its web interface and integrated into my ML workflows, and I am not directly involved in managing the infrastructure and the deployment configuration part.
I mainly use AWS alongside Comet for my machine learning workflows and cloud infrastructure, with Comet itself serving as the experiment tracking layer while the compute and other supporting services run under Amazon Web Services.
I would recommend Comet to teams that want a simple way to track, compare, and organize machine learning experiments, and if you are running multiple model iterations, I would definitely try it because the experiment history and the visualization make the workflow much easier to manage.