BinaryWrite method for webserver ActiveReports - memory intensive?

Posted by: cedarly on 4 August 2017, 2:55 pm EST

  • Posted 4 August 2017, 2:55 pm EST

    We are wondering if using the BinaryWrite method carries a high memory-usage overhead cost.

    We have a Classic ASP file that calls report dlls, and if it's going to be streamed to the browser, the dll returns the bytestream to the ASP file, which pushes it to a new browser window.

    Otherwise, the dll saves a file to a directory on the web server, returns the path, and the asp just re-directs the user to that file.

    It seems that the binaryWrite method is going to cause the bytestream to be held in memory - how is that memory location freed up? Should we be using the other methods where possible?

    thanks in advance for your expertise!


  • Replied 4 August 2017, 2:55 pm EST


    The memory should be cleared after the Response.End. The memory usage should be fairly equivalent with regards to streaming vs. saving the report to file. It is still the same report, and  exported  PDF stream in memory for both situations. The memory stream may be held slightly longer in memory when streaming to the client (as opposed to writing the file to the server), but the memory usage should be about the same.
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels