[CONFIRMED] Income Statement

[khush37]

The income statement page takes a while to load and when it loads, all the values are shown as $0.00.

[squaregatescrub]

same here.

[PolarMonkey]

I have the same thing. A lot of the items for this month are going to be 0$ so far, since we haven't had to make any maintenance, insurance, lease payments, etc. yet. The only thing that will be showing up will be from ticket sales, baggage fees and expenses for fuel, gates and landing fees.

As for the previous months, I'm going out on a limb here and blaming the pesky Y2K18 bug that's been going around. Maybe the way it looks up previous years doesn't take into account crossing over to a new year? Just tossing that out, could be completely wrong though.

[khush37]

I ran some quick flights last night and the income statement is showing the values of this month, however in the December and the November column the values are all still $0.00

[Unknown98]

I’ll look at it. Could be new route system isn’t inserting financials correctly. Or something wrong with how it looks up financial data with the new year

[Unknown98]

So the reason it loads slow is because there's over 1 million records in the financial transactions table in the database. Normally that isn't a problem, but because the income statement uses almost exclusively SUM aggregate functions to get the data, it slows it down significantly. As time goes on it will only become slower.

I'll see what I can do in the back-end to alleviate the issue. I'm having the same problem with the flight history database.

The $0 values for dec and november are because the game is trying to look up values for december 2018 rather than 2017. Working on that as well

[sw889432]

because the income statement uses almost exclusively SUM aggregate functions to get the data, it slows it down significantly

Sum the aggregate, warehouse the old data? Eg. At the end of the month, sum and store data, warehouse/archive the old stuff, and add total to the new month of transactions? Maybe indexing by months, then sum a month at a time.

I'm having the same problem with the flight history database.

Only thing I can think of is leveraging indexes. Make sure they cover the values you search by. That way, when looking up values, you are not searching the whole database, just what is in that particular index. Or when selecting data for the flight history page, do it by primary key, rather than one of your columns, and limit the range of data. Eg. page 1 selects (last key ) - (last key -50) kind of thing. That way it doesn't have to load all the data, search through it, then do the select. You may already doing this.

Lastly, set up some caching, and maybe use some database in between your SQL and the engine, that stores it in memory or only stores aggregated data for speed. Lastly, if you are scaling to the point where you just need more power, putting the SQL on its own server helps to scale easier.