--- title: "Dashboard Latency No Longer, 50% Cheaper MongoDB, Bounties for Answering Questions" date: 2025-05-09 number: 0237 url: https://railway.com/changelog/2025-05-09-latency --- # Dashboard Latency No Longer, 50% Cheaper MongoDB, Bounties for Answering Questions */bells chime, doves are released, balcony door flings open, crowd looks up expectantly * Hellooooooooo! It’s your friendly neighborhood changelog author here! */crowd is visibly confused* That’s right folks, today’s changelog is all about speed and there’s nothing more *divine* than speed! */crowd starts dispersing rapidly* This changelog is a *blessing* for your browser! */crowd empties out, tumbleweed rolls through the square, pigeon lands on changelog author* No but seriously folks, we do have a great one for you today. We’ve solved some major dashboard latency issues, we’ve increased single-threaded workload speeds on metal by 30%, we’ve shipped a Mongo optimization that reduces costs by more than 50% … and, well, you’ll have to read on below to see everything we did this week. Before we get started though, we wanted to remind you that [The Great Metal Migration](https://railway.com/changelog/2025-05-02-great-metal-migration#the-great-metal-migration) continues onward. Most of our team is working on the migration right now so we want to know ANY issue you run into. Seriously, if you have an issue migrating over to Railway Metal, make a ticket in [Central Station](https://station.railway.com/). We are prioritizing all metal reports until they go to zero. Meanwhile, we remind you to [read the docs](https://docs.railway.com/railway-metal) for everything you need to know about swapping over to Railway Metal. Ok? Ok! Let’s jump into the updates! ## Dashboard Latency No Longer [Image: We’ve eliminated most dashboard latency spikes] White smoke was coming from our ears a bit over the past couple weeks as we navigated some tricky latency issues with the Railway dashboard. But the smoke settled and we’re happy to kick off a new era of speedy dashboard performance with a fantastic new dashboard performance experience. If you’re curious, we solved a number of issues. One issue was related to our own internal code deployments. We deploy a lot of new code to Railway — many times a day, every day — and shipping those updates to many thousands of user sessions started causing a thundering herd problem in the canvas. Another problem we solved involved redundant queries to some external service providers and internal APIs. While yet another one involved the way we were handling websocket connections for stale sessions. … all in all, we’ve instituted a half-dozen or so optimizations that have resulted in a *much *faster dashboard experience *without* the latency blips that were impacting the dashboard over the past couple of weeks. Hurray! If you still run into any latency issues, we want to know about them. Hit us up on [Twitter](https://x.com/railway), [Discord](https://discord.com/invite/railway), or [Central Station](https://station.railway.com/). ## MongoDB Gets 50% Cheaper [Image: Mongo on metal is now 50% cheaper] Are you a [Mongo](https://docs.railway.com/guides/mongodb) user? Are you running on [Railway Metal](https://docs.railway.com/railway-metal)? Well we have some news for YOU. MongoDB is now *at least* 50% cheaper on Railway Metal (compared to non-metal instances) due to some new optimizations we made. How’s that possible, you ask? Well, as we’ve been saying for a while, Railway Metal allows us to deliver service that will ultimately be better, faster, cheaper, more configurable, and more reliable than our legacy “[cloud on a cloud](https://blog.railway.com/p/launch-week-02-welcome)” stack. This week, Mongo is an example of that. We found when running on metal that a certain default Mongo flag was improperly set. By changing the flag for default Mongo installs, we save you money. EZ-PZ Mongo Febreezy. Get started with a [Mongo template](https://railway.com/templates?q=mongo) today. ## Introducing Central Station Bounties! [Image: Bounties are now available to question-answerers in Central Station] If you’ve been a Railway passenger for a while, you should be familiar with [Central Station](https://station.railway.com/). It’s our one-stop shop for all your help and support needs on Railway … and since the day we decided to [home-roll Central Station](https://blog.railway.com/p/central-station) entirely, we’ve gone from solving dozens of tickets a day to many hundreds of tickets a day. As a result, we need to call in air support. From today, YOU can now answer public support tickets on Railway and we’ll pay you in credits to do so. Here’s how to get started: - Visit [station.railway.com/bounties](http://station.railway.com/bounties) - Select your workspace to receive reward credits - Provide answers for bountied threads - If your answer is accepted, you’ll get **$10 in credits** That $10-per-thread bounty is HUGE and it probably won’t last. But it’ll last at least this month as we seed the program before we start making it more reasonable. Sound like an interesting way to help people out in the Railway community and get rewarded for doing so? We think so too. [Get started ](https://station.railway.com/bounties)today. ✌️ ## Fixes and Improvements - We released a new SSH [tmux mode](https://github.com/railwayapp/cli/pull/628) available via `railway ssh --session`. This is useful if you need to run long-running tasks inside the deployment and want to make sure the command isn’t interrupted - We’ve been working a lot to tune [railway.com/new](http://railway.com/new) so be sure to check that out if you haven’t seen it in a little while