#PHP App Slow

33 messages · Page 1 of 1 (latest)

clear sluiceBOT
#

Project ID: 2124fa9a-2185-4e75-bcdb-71eab1dea145

nimble rapids
#

like, I have a application that sends requests to backend for fetching details

#

after one request has fully proccessed then the railway accepts other request

#

ultimately resulting into this

nimble rapids
#

why does it seem like only 1 thread is there, other requests do not continue untill the earlier requests have been sent out

fringe wing
#

just as I said in general chat, it's most likely a problem in app itself
could you share more info on what it is?

and just to avoid any confusion, me and the other folks who are around are not working for railway and so we can't just magically peek into your app

nimble rapids
#

Hello,
i have this problem

#

I have few requests being send to the backend to fetch some things
and the requests answered one by one

#

something like this

#

but in my case , I do not have a session_start() either

nimble rapids
nimble rapids
#

one request accepted, served then closed

#

then other one gets accepted

fringe wing
#

is keep alive enabled on the server?

#

oh Brody is here 😀

primal plover
#

i would like to state that this is not due to an issue with railway itself, that is all

fringe wing
#

🫡

nimble rapids
fringe wing
nimble rapids
fringe wing
#

too bad I don't work with php and can't tell you what exact steps you should try, but enabling keepalive is always a good idea

#

just enabling it may not solve this problem tho

torpid mortar
#

Are you using Nixpacks or a custom Dockerfile?

#

If you're using Nixpacks, it should be able to process either 32 or 50 connections simultaneously, depending on whether or not I'm reading the config file correctly

nimble rapids
#

seems some MaxRequestWorkers handler issue

#

its like this,

one request suceeded
then the server Acceptes the other request from the user and overall is slow asf