"The client is complaining that the data takes a long time to load."
Me, after investigating: "Does the client really need [not an exaggeration, actual figures] 130,000 rows of data?"
"I will show them these stats but they said they need it"

@wokeRoach I just have this image in my head of someone sat hunched over a desk inspecting all 130,000 rows of data.

130000 rows is a lot?
...

Of course it depends on the row size, but even on quite large rows, this is usually just a few seconds when working with a slow server.

@pda87 I assume this is on a database like mySQL or similar. How much data per row is it?

@AndSoWeCode @JohnScott
I agree that 130000 rows isn't an astronomical amount of data to retrieve, but I still stand by my statement of, "who needs to READ 130000 rows of data?!" And it's not a straightforward database hit, it requires some manipulation and calculations performed in C# before it is finally displayed. Hence that bottleneck is multiplied by...130000 :\

@pda87 I wish I could help you out dude.

@JohnScott It's all good, ranting about it helps :)

@pda87 still, 150k rows isn't a lot, even when processed.

I don't know the specifics of course, but when I export tens if millions of processed rows, it's needed, it's required, and I make it as fast as possible.

@pda87 for instance, are you leveraging all the hardware capacity at your disposal? Are you using parallel processing? Are you using it efficiently? What data structures and algorithms are used for processing? Can it be improved?