<@498057949541826571> Can we send otp as response for test env I am trying to fetch the generated c...
k
@rp_st Can we send otp as response for test env I am trying to fetch the generated code in createCodePost but couldn't find it
r
hey @krrishan you can log out the otp by overriding the sendEmail / sendSMS function in the backend sdk.
k
I don't want to log it I want either some constant otp every time or to send otp as response body for testing I tried modifying the response but still the generated otp is valid not the hardcoded received one
r
for a constant OTP, you can provide the userInputCode property to the input before calling originalImplmentation.createCode
k
last time similar issue occured when there was issue in supertoken core image So we updated to latest one
We have millions of users , there doesn't seem issue with cloud provider Please try if we can connect someday The issue lies in fetching the existingUser from supertoken
r
how many users have you migrated already?
k
60 lakhs
r
right, and so now, you are saying that getting a user based on id is taking time?
k
yeps
r
alright. We can get on a call.
let me send you a link
you can pick a time for tomorrow
k
Sure thanks so much let me connect with internal team and arrange a call
r
sure
hey @krrishan iv had to reschuedle it for day after since someone in my team is not available tomorrow. Sorry for the confusion
k
hi
r
hey @krrishan as discussed on call, i am happy to help out on discord. The core is behaving slowly for you with many users right? Which API are you querying (please provide the exact API path, method), and also provide details of how long that API call is taking, any error / info logs from the core, and also what queries are running in your database that are taking time. You can see the queries from a database inpsectore tool like pgadmin.
k
checkForExistingUser
r
once again, please answer my question precisely. I have reuqested for certain information. Please provide all
and also, confirm the version of the core you are using
k
For creating around 300-500 users in a minutes, CPU Usages is around 33% and number of active sessions are approx 25. if we migrate around 1000-1500 users per minutes, CPU usages becomes >90 % and active sessions are approx 33-34
r
this is very helpful information! thank you!
@sattvikc please see this ^^
we will get back to you @krrishan today / tomorrow after investigating from our side.
k
Thanks , waiting for your response
r
Also, can you confirm which version of the core you are running?
You can check based on the docker image tag
k
7.0
r
Ok thanks
Can you also click on the “top waits” tab and show the result?
k
Another issue , even on login sometimes we are getting 504 in /auth/consume api where we check for the existing user and verifies otp
r
This could be related to the same user id mapping query issue
k
sure just a moment
r
Ok thanks