# console.log large data set

**URL:** <https://community.postman.com/t/console-log-large-data-set/68694>\
**Category:** Help Hub\
**Tags:** console, performance, postman-console\
**Created:** [September 20, 2024, 8:18pm UTC](https://community.postman.com/t/console-log-large-data-set/68694 "2024-09-20T20:18:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![crashnorun](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@crashnorun](https://community.postman.com/u/crashnorun)\
**Post date:** [September 20, 2024, 8:18pm UTC](https://community.postman.com/t/console-log-large-data-set/68694/1 "2024-09-20T20:18:02Z")

</div>

Hi All,  
I have an endpoint that I am querying with Postman. This particular endpoint returns 50K objects of which contain an `ID`, `Name`, `Status`, and `Number`. On rare occasions I need to console log the returned data set, so that I can copy it to a text file and do some spot checking of the data. In the Post-response I have a for loop that console.logs the data. At first the logs come in pretty quickly but then it starts to slow down, and stall at times. Then it picks up again, and stalls again. I’ve checked the documentation as well as other posts on the forum, but couldn’t find if Postman has any limitations on console logging. Does anybody have any insights or similar experience they can shed some light on?

Also, is there a way to successfully cancel a query if it stalls? I’ve tried the Cancel button but that didn’t work. The only option that worked was to force quite Postman.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\
**Post date:** [October 20, 2024, 8:18pm UTC](https://community.postman.com/t/console-log-large-data-set/68694/2 "2024-10-20T20:18:54Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
