With my api call, I call some data from my own DB

With Prisma

The db is not local

You will probably need to profile some stuff in your api, see which parts are taking how much in what environments.

The call to your Route Handler and its response can probably not be made any faster with just code changes.

You might have to optimize your code depending on what you have in your code. If its just a prisma call then maybe its just that the database calls and responses are taking too long.

in local it’s 100ms and deploy 300-400ms

I changed a lot so far

Removed unnecessary Prisma calls

Could I maybe use the edge api? Is Prisma available there

oh i figured out smth, in local the content encoding is: gzip while on prod its on: br and when i check the answer there is no "security" tab on the network

prod

local

i guess its because vercel

maybe thats why? it takes longer?

local

prod

So subsequent calls to vercel take as long?

Keep in mind there’s a cold start

For the first call

And if you’re communicating with dbs or external services

ye its not the cold start

There’s latency

i do 1-2 calls b4

to test it

i do that in both ways

one is localhost one is prod

If you really need low latency responses

prod

local

If you turn some of those api routes to edge

i looked about edge functions

is it hard to implement?

im using prisma

Depends

But I think prisma has support via data proxy

ye

Before doing any of that

saw some videos about that

Consider if you really need this

its a guessing game

where the user sees the result

after guessing

Oh edge can be perfect for this

Or you can use pusher or ably

To do websockets for real time communication

what is that?

Pretty commonly used along side a vercel app

If you need real time

But don’t want to manage the infrastructure yourself

mhmmm

im doint some maths in the api call

But it totally depends on what you’re doing

Just an alternative to consider

wait can i dm u

ah and btw, the call is 100ms faster when im not logged in on prod so 350 instead of 450 and 83ms instead of 100-110ms on local

cause there are some more things the api does when logged in

No I don’t do dms sorry

Do you use next-auth

no i use clerk

Ah okay

when the user is logged in and plays it gets to the leaderboard

etc

but i guess i should give edge a try right

or this

Edge first

do i have to change alot?

Hopefully no

i saw smth like i need a prisma smth acc

But if you’re using node only APIs

They may not work

mhmm what u mean by that

Uhhh

Just read the docs on edge

To get it fully explained

But basically

oke ill give it a try i guess

Edge has a limited set of APIs available

Otherwise everyone would be running on it

prisma should work i guess

Yes with their edge specific configs, etc

ye

what u think

how would the ms get

from 350-450ms

to 100-200?

or even less

Hard to say

Just try it out with a simple api function

And see for yourself.

ye ill do that

thanks for ur help so far

@linesofcode im currently tryin to use edge,

prisma generate --data-proxy

Prisma schema loaded from prisma/schema.prisma
✔ Generated Prisma Client (v5.2.0, engine=none) to ./node_modules/@prisma/client in 79ms
Start using Prisma Client in Node.js (See: https://pris.ly/d/client)

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)

import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()

does it load the normal prisma one?

✔ Generated Prisma Client (v5.2.0, engine=none) to ./node_modules/@prisma/client in 79ms

i guess its using the normal one right

Take a look at this

I dont use prisma btw

so the only advice I can give you is high-level

i did this

i had to use this:
iin my package.json scripts:
"postinstall": "prisma generate --data-proxy"

i added --data-proxy

but its no there

.

i got it workin

thanks alot

from 350ms to 100 when not logged in and 450ms to 150ms when logged in

even in localhost it got so much faster

100ms -> 40-50ms

Awesome!

congrats

@linesofcode quick question, when i use edge functions, do i have to make every api call and edge function calll?

can you rephrase that question please?

i changed my api call to an edge api call right

as u mentioned

but do i have to change every call now to an edge function?

yeah

the ones you deem are necessary

to be turned into edge functions

should be turned into edge functions

at least thats how I approach the problem

idk if prisma data proxy has other opinions

oh i see

currently i have 4 api calls i do change them all now to edge functions

If that’s what you need, then yes