Postman: issue with scaling, perhaps turn off response printing?

Viewed 8

I have an API that returns the values for n rows in a csv file.

If the table is 100 "rows" (for lack of a better term) and I get the values in every row, it takes x seconds and has a size of y KB.
If the table is 100 rows and I get the values for half the rows, it takes ~x/2 seconds and has a size of ~y/2.
This makes sense.

The problem comes when I get to the real size of the file -- millions of rows. It's not giving me the correct values. The sizes and times don't pass the smell test (they're too low), and they're the same.
The values in the entire table, half the table, whatever -- the time it takes to return the values are the same and the size of what's being returned is the same.

I have a suspicion that it's the printed response. What... it's gonna print four million rows in that wee little panel at the bottom of the screen?

Is there a way to just get the metadata (status, time, size) and not print the response? A setting or something? That's all I need anyways.

(PS: Response is JSON if that matters)

0 Answers
Related