Good morning, I've added recently email verification to my app. However now one the user first loads the page, the verify call takes like 6 seconds, also it calls the verify email api 2. Im pretty sure im doing something incorrectly 😅

hey @drixhua

yes, im hosting it with docker

right. So you might want to see what is the slow part - the core or the backend process running the backend SDK

bot GET requests

are you on react dev build with strict mode?

yes, strict mode

can you remove the strict mode? Or then try in a production build? Maybe the 2 calls to verify won't happen then

Indeed, thank you I will try

awesome!

I think for the signup is also taking a while

Right. One quick test you could do is to connect your backend to our managed service and see if it’s still slow. If it is, then the issue is your backend process (that’s running our backend SDK). Else it’s on the core you are running.

Hi, I switched to manage service and now seems to load quite fast. Do you know how I can debugg my docker container to see what's wrong? Thank you

Check the RAM / CPU cores available. We recommend giving 500 mb ram and 2 CPU cores for great performance. Issues could also be if you are on apple m1 / m2 acrhitecture and have docker or the db thats not natively built for ARM. I suggest using a cloud service instead of your local machine to run the core.

I was using 512mb ram and 1CPU and changed now to 4gb ram and 1 CPU was is taking still around 7 s to complete the sign in request

hmm. Try deplpoying on an ec2 instance?

thank you, will try

right

mmm still taking to long

Is it the same query that’s taking time? Where is the db hosted? And where was it hosted before when the query took 6 seconds?

yes, the same query, the db is hosted in digital ocean and was also hosted there before

Could you try another db?

sorry, what do you mean by trying another db?

That’s not hosted on digital ocean

I could create one in AWS yes

Doesn’t seem to be missing anything

Checking the database logs for the signinup request it shows this error. Maybe is related?

2023-12-24 15:52:28 UTC::@:[398]:LOG:  checkpoint starting: time
2023-12-24 15:52:28 UTC::@:[398]:LOG:  checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.108 s, sync=0.003 s, total=0.113 s; sync files=2, longest=0.002 s, average=0.002 s; distance=65484 kB, estimate=65561 kB
2023-12-24 15:54:13 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:ERROR:  duplicate key value violates unique constraint "thirdparty_user_to_tenant_third_party_user_id_key"
2023-12-24 15:54:13 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:DETAIL:  Key (app_id, tenant_id, third_party_id, third_party_user_id)=(public, public, google, 106204688582746280271) already exists.
2023-12-24 15:54:13 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:STATEMENT:  INSERT INTO thirdparty_user_to_tenant(app_id, tenant_id, user_id, third_party_id, third_party_user_id) VALUES($1, $2, $3, $4, $5)
2023-12-24 15:54:14 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:ERROR:  duplicate key value violates unique constraint "emailverification_verified_emails_pkey"
2023-12-24 15:54:14 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:DETAIL:  Key (app_id, user_id, email)=(public, 240ad2d3-7c2e-47ab-b6bc-31e0aa7938d6, asdsad@gmail.com) already exists.
2023-12-24 15:54:14 UTC:64.226.88.158(46770):postgres@supertokens:[8158]:STATEMENT:  INSERT INTO emailverification_verified_emails(app_id, user_id, email) VALUES($1, $2, $3)

That’s all ok.

no, the core is running in digital ocean as a docker container

Hmm.

the database is in aws

Im not sure why this would be happening honestly

Allright, no worries

Yup. If you find anything specifically wrong with supertokens, let us know. We can of course help with that