RDLC report performance

geordie
geordie Member Posts: 655
edited 2014-03-10 in NAV Three Tier
Hi, I was reading this post from NAV team regarding RDLC performance and out of memory exceptions.
Except the suggestions regarding dataset reduction (in terms of lines and columns), it's interesting the solution of taking advantage of server side printing to avoid the 32bit client bottleneck through job queue: anyone tried this method, maybe with reports generating a big amount of data like detail trial balance? Any recommendation against use it?
* Daniele Rebussi * | * Rebu NAV Diary *

Comments

  • lohndorf
    lohndorf Member Posts: 2
    Last week I had an OutOfMemory report (report 4). Then I ran the report with SAVEASPDF, and it successfully created a 27.000 page report in 2 1/2 hours. So for me, moving it to server-side worked very well, creating around 10.000 pages per hour. It did slow down the NST quite a lot while it was creating the PDF (as expected), so in a live system I would have set up a separate NST for this.

    I'm also interested to hear about other's experiences with this,


    /Lars

Categories