Gielinor Gains depends heavily on OSRS Wiki data. When that pipeline feels fragile, users feel it immediately.
This post was the planning note for a leaner data flow: fewer repeated timeseries pulls, more local structure, and less pressure on shared infrastructure.
The issue
- A single item update could still force a full timeseries pull.
- Caching helped, but it could not eliminate the cost of repeated historical reads.
- More RuneScape tools and AI-powered projects were increasing pressure on shared Wiki infrastructure.
- Every large aggregation also meant more compute work on the Gielinor Gains side.
The better path
The plan was to use the Wiki 5-minute feed, hydrate a local timeseries store, and let Gielinor Gains query that local structure for scoring and display.
That should reduce Wiki calls by orders of magnitude, make refresh paths more stable, and keep the site from repeatedly asking for data it already knows how to store.
What does not change
The mission stays the same: keep Gielinor Gains free, ad-free, and useful for flippers who want to know what to buy, when to try it, and how much capital to put behind it.
Plenty of tools publish raw data. The goal here is a cleaner decision-making experience built on honest signals and a data pipeline that can actually hold up.