yes, but I call it outside of the loop that iterates over chunks like so ```Typescript const { reada

yes, but I call it outside of the loop that iterates over chunks like so

const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();

                    try {
                        for await (const chunk of completions) {
                            const content = chunk['choices'][0].delta.content!;
                            const encodedMessage = encoder.encode(content);
                            writer.write(encodedMessage);
                        }
                        writer.close();
                        return new Response(readable, {
                            headers: {
                                ...corsHeaders,
                            },
                        });
                    } catch (e) {
                        console.error(e);
                        // writer.abort(e);
                        return new Response('bad bad error', { headers: corsHeaders });
                    }

const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();

                    try {
                        for await (const chunk of completions) {
                            const content = chunk['choices'][0].delta.content!;
                            const encodedMessage = encoder.encode(content);
                            writer.write(encodedMessage);
                        }
                        writer.close();
                        return new Response(readable, {
                            headers: {
                                ...corsHeaders,
                            },
                        });
                    } catch (e) {
                        console.error(e);
                        // writer.abort(e);
                        return new Response('bad bad error', { headers: corsHeaders });
                    }

const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();

                    try {
                        for await (const chunk of completions) {
                            const content = chunk['choices'][0].delta.content!;
                            const encodedMessage = encoder.encode(content);
                            writer.write(encodedMessage);
                        }
                        writer.close();
                        return new Response(readable, {
                            headers: {
                                ...corsHeaders,
                            },
                        });
                    } catch (e) {
                        console.error(e);
                        // writer.abort(e);
                        return new Response('bad bad error', { headers: corsHeaders });
                    }

const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();

                    try {
                        for await (const chunk of completions) {
                            const content = chunk['choices'][0].delta.content!;
                            const encodedMessage = encoder.encode(content);
                            writer.write(encodedMessage);
                        }
                        writer.close();
                        return new Response(readable, {
                            headers: {
                                ...corsHeaders,
                            },
                        });
                    } catch (e) {
                        console.error(e);
                        // writer.abort(e);
                        return new Response('bad bad error', { headers: corsHeaders });
                    }

Bbkyerv yes, but I call it outside of the loop that iterates over chunks like so ```Type...

Hello, I’m Allie!•9/19/23, 12:06 PM

Oh yeah, you have to return the response before you write to the WritableStreamWritableStream

Hello, I’m Allie!•9/19/23, 12:07 PM

Otherwise it will wait for it to finish before returning

bkyervOP•9/19/23, 12:09 PM

if I move the return statements above the loop the whole loop will not be executed. Can you please point more precisely where exactly I need tto move the returning the response?

matt•9/19/23, 12:17 PM

@bkyerv is this not working? https://developers.cloudflare.com/workers/examples/openai-sdk-streaming/

Bbkyerv if I move the return statements above the loop the whole loop will not be execut...

Hello, I’m Allie!•9/19/23, 12:42 PM

Wrap the loop in an async function then put it in a waitUntil

bkyervOP•9/19/23, 12:43 PM

@m.a.t.t.t it does, but the way it's set up essentially negates the benefits of streaming. The issue is that it waits for all chunks from the OpenAI completion to be written into the stream before sending the entire response to the client. This behavior is contrary to the expectations of users, including myself and another individual who opened a ticket in the help section. We anticipate that the response should be streamed to the client in smaller, incremental pieces. To achieve this, the following changes need to be made:

Typescript 
const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();
                    const response = new Response(readable, {
                        headers: {
                            ...corsHeaders,
                        },
                    });
                    (async () => {
                        try {
                            for await (const chunk of completions) {
                                const content = chunk['choices'][0].delta.content!;
                                const encodedMessage = encoder.encode(content);
                                writer.write(encodedMessage);
                            }
                            writer.close();
                        } catch (e) {
                            console.error(e);
                            // writer.abort(e);
                            return new Response('bad bad error', { headers: corsHeaders });
                        }
                    })();
                    return response;

Typescript 
const { readable, writable } = new TransformStream();

                    const writer = writable.getWriter();
                    const encoder = new TextEncoder();
                    const response = new Response(readable, {
                        headers: {
                            ...corsHeaders,
                        },
                    });
                    (async () => {
                        try {
                            for await (const chunk of completions) {
                                const content = chunk['choices'][0].delta.content!;
                                const encodedMessage = encoder.encode(content);
                                writer.write(encodedMessage);
                            }
                            writer.close();
                        } catch (e) {
                            console.error(e);
                            // writer.abort(e);
                            return new Response('bad bad error', { headers: corsHeaders });
                        }
                    })();
                    return response;

HHello, I’m Allie!Wrap the loop in an async function then put it in a waitUntil

bkyervOP•9/19/23, 12:45 PM

Thank you, that's what I ended up doing by talking to chatgpt)) In general, can you please suggest some resources to learn more about streams. Not in million years I would guess that response needs to be constructed before starting to write into stream. Also what is the need for waitUntil?

Bbkyerv Thank you, that's what I ended up doing by talking to chatgpt)) In general, can ...

Hello, I’m Allie!•9/19/23, 12:45 PM

If you don’t use waitUntil then it will cut off the loop once you return a Response

sathoro•9/19/23, 1:02 PM

yeah that doc (https://developers.cloudflare.com/workers/examples/openai-sdk-streaming/) needs to be updated lol

HHello, I’m Allie!Wrap the loop in an async function then put it in a waitUntil

sathoro•9/19/23, 1:03 PM

this is what we do in prod, works great

Elliot Hesp•9/19/23, 2:01 PM

When using the cache within a worker, does it autoamtically apply a cache-control header if cached? I don't set one when I store it in cache, but there seems to be one there with a value of 1440014400

✦

✦ xcaeser•9/19/23, 2:50 PM

tried workers for the first time. usually on aws lambda and vercel functions...

✦

✦ xcaeser•9/19/23, 2:51 PM

this is vercel

✦

✦ xcaeser•9/19/23, 2:51 PM

this is aws

✦

✦ xcaeser•9/19/23, 2:51 PM

and this workers LMAO

✦✦ xcaeser and this workers LMAO

Hello, I’m Allie!•9/19/23, 2:52 PM

What does your code do?

✦

✦ xcaeser•9/19/23, 2:52 PM

same code, nodejs, TypeScript on vercel and workers, mjs on aws (1GB disk + 1GB RAM)

HHello, I’m Allie!What does your code do?

✦

✦ xcaeser•9/19/23, 2:52 PM

uses cloudflare KV,

✦

✦ xcaeser•9/19/23, 2:52 PM

just basic CRUD

✦

✦ xcaeser•9/19/23, 2:53 PM

vercel and aws use vercel kv (which is upstash)

✦✦ xcaeser uses cloudflare KV,

Hello, I’m Allie!•9/19/23, 2:53 PM

What does it show with a hot read?

Hello, I’m Allie!•9/19/23, 2:54 PM

Also, wouldn't this more be a comparison of CF KV vs. Upstash?

Hello, I’m Allie!•9/19/23, 2:54 PM

Since the code is just doing reads no matter what?

Hello, I’m Allie!•9/19/23, 2:54 PM

Wonder if it were faster/slower if you read from Upstash with Workers...

✦

✦ xcaeser•9/19/23, 2:55 PM

what's behind cloudflare kv?

✦

✦ xcaeser•9/19/23, 2:55 PM

i'll just put these here

✦

✦ xcaeser•9/19/23, 2:56 PM

again, first time trying out cloudflare, but hard to be aws

✦✦ xcaeser what's behind cloudflare kv?

Hello, I’m Allie!•9/19/23, 2:56 PM

Proprietary storage engine afaik

HHello, I’m Allie!Wonder if it were faster/slower if you read from Upstash with Workers...

✦

✦ xcaeser•9/19/23, 2:57 PM

shouldn't KV be optimized for workers? and maybe closer in region?

HHello, I’m Allie!Proprietary storage engine afaik

✦

✦ xcaeser•9/19/23, 2:57 PM

should've gone for foundation db

✦✦ xcaeser shouldn't KV be optimized for workers? and maybe closer in region?

Hello, I’m Allie!•9/19/23, 2:57 PM

There is some work being done on it, but right now it is dual-zone Europe and Americas with a cache

Hello, I’m Allie!•9/19/23, 2:57 PM

So if you aren’t in the US/EU, you might get slower reads

✦

✦ xcaeser•9/19/23, 2:58 PM

I'm in paris

✦

✦ xcaeser•9/19/23, 2:59 PM

developer exp is top notch tho (from terminal as well), way better than raw aws

✦✦ xcaeser should've gone for foundation db

Hello, I’m Allie!•9/19/23, 3:00 PM

FoundationDB(Apache licensed) was released just 5 months before KV, so it might have been that they started work on it before it was viable

Hello, I’m Allie!•9/19/23, 3:01 PM

Though I would note too that Vercel Edge is Workers too

Hello, I’m Allie!•9/19/23, 3:01 PM

So for any non-platform-bound applications, they should perform about the same

HHello, I’m Allie!Though I would note too that Vercel Edge is Workers too

✦

✦ xcaeser•9/19/23, 3:01 PM

nop it's aws afaik

✦✦ xcaeser nop it's aws afaik

Hello, I’m Allie!•9/19/23, 3:05 PM

That’s their core(I.E. non-Edge). That’s also why they are so particular about the APIs that the Edge Runtime does and doesn’t support

Hello, I’m Allie!•9/19/23, 3:05 PM

Because the Edge Runtime(WorkerD) is V8, but not Node

Hello, I’m Allie!•9/19/23, 3:06 PM

https://news.ycombinator.com/item?id=29003514

leerob

Vercel's Edge Functions are built on top of Cloudflare Workers. The runtime is designed for any similar provider, but we've chosen Cloudflare for now because they have an amazing product.