Showing posts with label accelerate. Show all posts
Showing posts with label accelerate. Show all posts

Sunday, March 11, 2012

Accelerating first call of Reports

Hi,
is there a possibility to accelerate the first call of a report?
It could take up to 1 minute on my Server. After I called a report the first
time, its going faster (~5 seconds).
Thanks and regards,
StefanThis is due to IIS, not Report Server specifically.
Go to IIS Manager, under Applocation Pools node, right click
"DefaultAppPool" in which the Reporting Server work process is running,
select properties. On "Performace" tag, you will see, by default, the app
pool will shut down if > being idle for 20 min. You can extend this time to
8x60min 480min, so that the app pool will not shut down for a regular
working day. However, the first report reader of the day, will hit the
delay. You may schedule a dummy report at beginning of a work day for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stefan" <stefan@.nospam.nospam> wrote in message
news:eIt4iTroHHA.1476@.TK2MSFTNGP03.phx.gbl...
> Hi,
> is there a possibility to accelerate the first call of a report?
> It could take up to 1 minute on my Server. After I called a report the
> first time, its going faster (~5 seconds).
> Thanks and regards,
> Stefan
>|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Bruce, hi Wei Lu,
thanks for your support.
Can you please give me an example, how to call a dummy report from a
batch-File.
Thanks and regards,
Stefan
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> schrieb im Newsbeitrag
news:eZ%23UFCsoHHA.4516@.TK2MSFTNGP05.phx.gbl...
> This is due to IIS, not Report Server specifically.
> Go to IIS Manager, under Applocation Pools node, right click
> "DefaultAppPool" in which the Reporting Server work process is running,
> select properties. On "Performace" tag, you will see, by default, the app
> pool will shut down if > being idle for 20 min. You can extend this time
> to 8x60min 480min, so that the app pool will not shut down for a regular
> working day. However, the first report reader of the day, will hit the
> delay. You may schedule a dummy report at beginning of a work day for
> this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Stefan" <stefan@.nospam.nospam> wrote in message
> news:eIt4iTroHHA.1476@.TK2MSFTNGP03.phx.gbl...
>> Hi,
>> is there a possibility to accelerate the first call of a report?
>> It could take up to 1 minute on my Server. After I called a report the
>> first time, its going faster (~5 seconds).
>> Thanks and regards,
>> Stefan
>|||Hello Stefan,
I did not have a sample yet. I would like to suggest you create a
application to use the web services to call the reports.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
I run the following script in planned tasks and now everything runs fine.
Thanks,
Stefan
Option Explicit
Dim objIEA
Set objIEA = CreateObject("InternetExplorer.Application")
objIEA.Navigate
"http://localhost/reportserver?%2fReports2fMyDummyReport&rs:Command=Render"
objIEA.visible = true
While objIEA.Busy
Wend
objIEA.Quit
Set objIEA = Nothing
"Stefan" <stefan@.nospam.nospam> schrieb im Newsbeitrag
news:O%23d1KDopHHA.4632@.TK2MSFTNGP04.phx.gbl...
> Hi Bruce, hi Wei Lu,
> thanks for your support.
> Can you please give me an example, how to call a dummy report from a
> batch-File.
> Thanks and regards,
> Stefan
>
>

Accelerate Sql Express?

Hi,

we're planning to migrate an existing dataset cache mechanism to Sql Server Express. The dataset isn't really able to handle and search one million recordsets any more :-)

Once a day the Cache Sql Database wil be filled with fresh data. In comparison with the dataset takes up to fourty times longer to build the cache on the same machine!! Ok, I expected that i will take longer than creating the objects in a database with all its "overhead" like atomic transactions etc. But not so much.

The current throughput on SQL Server ist nearly 400 inserted records per second in the same table. The dataset stores up to 17.000 of the same data.

I'm wondering about the the following fact. Allthough I'm testing the Mass-Inserts with generating synthetic records in a unlimited for-loop, the server CPU load is allways less than 3 %. For all I care it could be much higher while the nightly process of initilializing the cache. Could there be a unnecessary throttle that limits the amount of inserts per second?

Any ideas how to accelerate the database engine or optimizing bulk-inserts?

P.S. I tested some different options and played around with connection string options like packekt size, Named Pipes connections, recycling the last commando and parameters and so on. Without any significant effects..

Marcus

Could you post how you are doing the inserts are the moment? Are you using BULK INSERT or bcp, or are you doing regular inserts? Also, what is the transaction size you are using, and what are the specifications or your machine, disks, etc.|||Im inserting each record in a single regular insert statement via ADO.NET (2.0) ExecuteComand. As far as I know, buldinsert are only for files available, right?

The Maschine is a 4 x XEON 3,6 Ghz, 32 bit Win2003 Server Sp1, 4GB Ram and a fast SCSI Raid

What is the transaction size? Is this a configurable value? At the moment all values are unchanged
installation defaults.

Thanks
Marcus|||There are several ways to speedup:

1) Use a SqlTransaction in your ADO.NET code, and issue a commit after every N rows that you insert. If you don't do this, a commit will be done for each row, which is very expensive.

2) To get big perf improvements, you should use BulkInsert or BCP to bulk load your data in your database. These methods are much faster than doing individual inserts.

Thanks,