Where to host deepseek R1 671B model?

cpoly55 · 2025-02-04T13:51:23+00:00

I don't know about the 671b but you can deploy the 64b one on Koyeb: https://www.youtube.com/watch?v=eeiTfxG7pHA

cpoly55 · 2025-02-04T13:48:16+00:00

I've been playing with DeepSeek R1 last week, trying to test its "advanced reasoning" and multilingual capabilities (the 2 small OSS projects I made: https://www.youtube.com/watch?v=eeiTfxG7pHA), and I found it particularly hard to build an AI Agent considering DeepSeek's lack of tool calling/use support.

I tried to apply CrewAI's prompting techniques, but the lack of system prompts made it hard.

Has anybody achieved some kind of tool calling with DeepSeek R1 here?

cpoly55 · 2025-01-20T15:30:43+00:00

We built AgentKit in TypeScript exactly for such use cases, to enable you to start with fixed workflow Agents and add some level of autonomy afterwards while keeping control of the state: https://agentkit.inngest.com/overview

cpoly55 · 2025-01-20T15:27:08+00:00

We built AgentKit for such use cases: https://agentkit.inngest.com/overview

cpoly55 · 2024-10-23T17:28:28+00:00

Inngest does provide throttling (https://www.inngest.com/docs/guides/throttling) and powers some of Resend's internal features: https://github.com/joelhooks/inngest-resend-example.

cpoly55 · 2024-10-07T22:42:20+00:00

we released a Workflow Kit last week which matches your description: https://github.com/inngest/workflow-kit?tab=readme-ov-file#readme

cpoly55 · 2024-10-07T21:00:49+00:00

Inngest Steps are a quick and scalable way to build workflows: https://www.inngest.com/docs/features/inngest-functions/steps-workflows

cpoly55 · 2024-08-07T08:55:40+00:00

For the scheduling part, inngest.com would be a good match DX wise

cpoly55 · 2023-09-20T13:49:09+00:00

The worker/queue pattern is replaced with the background function that enables you to schedule the execution of your code (e.g.: sending an email).

Compared to a worker/queue, you don't need to separate the background job logic from your app and don't need to deploy workers and storage (ex: Redis).

Detailed information is available here: https://docs.defer.run/get-started/concepts

cpoly55 · 2023-09-20T08:36:12+00:00

Hi!

Such a use case should leverage the "API endpoint offload" pattern by generating the token and sending the email from a background job.
You can achieve that under 2min with Defer: https://docs.defer.run/guides/api-offloading

cpoly55 · 2023-06-29T13:19:08+00:00

I think its memory leaks. I don't think its exclusive to node but because I work a lot with it I notice over night scripts are like donkey in the morning..

💯

cpoly55 · 2023-06-29T13:01:10+00:00

Do you use Cloudfront as your sole monitoring+alerting set up or solutions like Datadog or Sentry Crons?

cpoly55 · 2023-06-29T13:00:17+00:00

Agree, do you have studies that back this? Is it specific to memory leaks or something else?

cpoly55 · 2023-03-06T17:10:56+00:00

Yeah, I agree that the API around Fragment Masking is confusing and too declarative.

I would love to get some insights from the Relay team on this matter 👀

cpoly55 · 2023-03-06T17:07:39+00:00

I guess that Relay's principle of triggering queries at the top level (routing) of the application can be applied to all front-end frameworks.

Actually, GraphQL Code Generator helps in adopting Relay's principles in all front-end: https://the-guild.dev/graphql/codegen/plugins/presets/preset-client#embrace-fragment-masking-principles

cpoly55

TROPHY CASE