6 ms·
Thanks for the tips! I'll take a look - requests are typically super fast, so perhaps the database is just under high load due to launch. I'll check now. (I run
by philip1209 3y ago
Thanks for the tips! I'll take a look - requests are typically super fast, so perhaps the database is just under high load due to launch. I'll check now. (I run replicas in a couple cities on https://fly.io https://fly.io, so general latency should be low too.)
For the filenames - I'll take a look. I'm using some popular libraries for files, which I hope address things like this.
- qingcharles 3y agoIf you're allowing image uploads, always make sure it is an image being uploaded. I rooted a very big webhost back in the day by uploading a script as a PFP. Funnily enough, I found their root password eventually in a config file. It was "internet" :|
- mdaniel 3y agoI can now say that unless you are still, at this very moment, under "launch duress" it's just the site's steady state because it still takes exactly 1.68 seconds to load the first link of that site, and 1.89 seconds to load the /replies endpoint on it, and -- as I thought I helpfully pointed out -- clicking that link does nothing for almost 2 seconds, leading the user to believe it's borked I'm glad you have spent all this energy reinventing ruby on rails based forums, but this is not the way or, actually, in the spirit of being constructive: what is your experience clicking on those links? does it shows some loading indicator for you? does it load faster than 2 seconds for you?
- philip1209 3y agoHey, thanks for the follow-up. While traffic on the marketing website has decreased since launch, traffic on the main app has increased. I do some performance monitoring (using https://skylight.io https://skylight.io) and have identified some opportunities for speed-up. I'm working on getting those updated. I also just resized the database - it seems that some read queries were being slow. I'm continuing to dig into the postgres settings and indexes to make sure everything is good, too. -- Update: I'm seeing ~300ms responses on each of those endpoints now in my browser.