![]() ![]() But even if I disable logging of my own statements, it still writes the stuff like:Įtc, and that seems to take some time to. I have even started wrapping all my console.log statements within a debug-check, and then have flag in the globals file to tell if it should log to file or not. Even hiding the network logs (In Postman Console) does not seem to affect this for the better. Memory after the tests are done (but Postman still using CPU):įor a test that ran for approximately 5 minutes, It takes at least another 15-30 minutes before it is done logging all the requests (With console.log) to file. I only need them for debugging purposes, which is why I would like to have this feature. Very often while executing the tests, I never look at these logs. (1-2 seconds to switch between two request-tabs)Īfter the requests are done, I would expect that cpu would/should drop to around 0% cpu again, but that is not the case:Īnd the only thing I can tell that Postman is doing at this time is write to Postman Console / log. Not that high at all, but changing between tabs in postman is really sluggish now. ![]() Running a collection with only 11 requests (but with some being ran several times until an event has been indexed in the system under test), with 10 iterasions. To open the Postman console, head to 'View' in the application menu, and click on 'Show Postman Console' or use the keyboard shortcut (CMD/CTRL + ALT + C). (Transition from Linux to Mac was extreme with regards to how much faster Postman feels on Mac compared to on Linux by the way) ![]() Postman is responsive and working as it expected. Restarting Postman v8.0.4, cpu is at around 0% CPU: But kind of new to mac, so using Activity Monitor and timing manually. Right, tried to figure out how to get a good log of this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |