title: Postman: issue with scaling, perhaps turn off response printing?
body: <p>I have an API that returns the values for <code>n</code> rows in a csv file.</p>
  <p>If the table is 100 &quot;rows&quot; (for lack of a better term) and I get the values in every row, it takes <code>x</code> seconds and has a size of <code>y</code> KB. <br/>If the table is 100 rows and I get the values for <strong>half</strong> the rows, it takes <code>~x/2</code> seconds and has a size of <code>~y/2</code>.<br/>This makes sense.</p>
  <p>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 <em>they're the same</em>.<br/>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.</p>
  <p>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?</p>
  <p>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.</p>
  <p>(PS: Response is JSON if that matters)</p>