this post was submitted on 20 Jun 2024
471 points (89.7% liked)
Technology
57453 readers
4635 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've used crewai and autogen in production... And I still agree with the person you're replying to.
The 2 main problems with agentic approaches I've discovered this far:
One mistake or hallucination will propagate to the rest of the agentic task. I've even tried adding a QA agent for this purpose but what ends up happening is those agents aren't reliable and also leads to the main issue:
It's very expensive to run and rerun agents at scale. The scaling factor of each agent being able to call another agent means that you can end up with an exponentially growing number of calls. My colleague at one point ran a job that cost $15 for what could have been a simple task.
One last consideration: the current LLM providers are very aware of these issues or they wouldn't be as concerned with finding "clean" data to scrape from the web vs using agents to train agents.
If you're using crewai btw, be aware there is some builtin telemetry with the library. I have a wrapper to remove that telemetry if you're interested in the code.
Personally, I'm kinda done with LLMs for now and have moved back to my original machine learning pursuits in bioinformatics.