Improve performance #49

New issue

Open

opened 2026-03-12 02:45:45 +00:00 by maxtkc · 1 comment

maxtkc commented

2026-03-12 02:45:45 +00:00

Owner

Right now, the load test (#11) showed challenges in handling higher numbers of vehicles. There is a lot of room for improvement.

A few notes:

Lets calculate the latency when we fetch the feeds so we know how behind the server is
logging is a likely culprit for slowdowns, lets reduce it
we can try with just vehicle position updates to see if it's the up-dogger lagging
Lets not add more resources until we make the basic optimizations

Right now, the load test (#11) showed challenges in handling higher numbers of vehicles. There is a lot of room for improvement. A few notes: - Lets calculate the latency when we fetch the feeds so we know how behind the server is - logging is a likely culprit for slowdowns, lets reduce it - we can try with just vehicle position updates to see if it's the up-dogger lagging - Lets not add more resources until we make the basic optimizations

maxtkc added the

labels

2026-03-12 02:45:45 +00:00

maxtkc self-assigned this

2026-03-12 02:45:45 +00:00

maxtkc added this to the GTFS Realtime project

2026-03-12 02:45:45 +00:00

maxtkc commented

2026-03-19 01:10:45 +00:00

Author

Owner

This is important for the Amtrak bridge, which would be really good for getting things off the ground

Maybe we can have loaders and then a separate latency checker that sends individual pings along a route trying to see delays. This way we can set a baseline for when it's running smoothly and then when it's slow. This is important for the Amtrak bridge, which would be really good for getting things off the ground