You are not logged in.
We need your support for getting minimum & recommended hardware requirements for ReportServer. version 3.0.5 (RAM/No of Cores). If you can provide us hardware specification for that, that would be really great.
Thanks
Thanks & Regards
Nayana
Offline
A Reporting system usually consists of three components: database, web server and front end. for better performance try to balance the components.
the database will need to deliver performance regarding
- the complexity of the queries (processor)
- the number of parallel queries running (processor, memory) and
- the size of the result set (I/O capacity).
try to have a fast database, that is the number one performance issue. fast is defined by the two parameters just mentioned. Hardware wise have SSD'S, if that is not enough have separate controllers for I/O for your database.
Once you have a fast database rs performance depends on
- number of parallel executions (processor / memory)
- complexity of report design / output. I's a huge difference if you create a nice report or a simple list.
Creating complex Excel Sheets via jxls can be very time and memory consuming !
Sizing is always a matter of the actual work load, you can have many users with few fast queries scheduled at night and a small system is fine. vice versa you can have few users with complex reporting and a poor database and no one will like the performance ... . Performance is ever changing and has to be monitored on a regular base.
Hope that gives you a starting point for your analysis.
wbr jan
Offline
Hi Nayana,
further, keep in mind the connection pool:
your db has a max number of sessions defined. This parameter defines the maximum number of sessions available at a given point in time. To increase the maxIdleTime means to occupy the connections longer, thus resulting in less sessions available for your connections. When all sessions in the reportserver's session pool are occupied, no report execution is possible (no connection available). Therefore, increase the number of sessions in the session pool (maxPoolSize) only if the max number of sessions of your database allows it. Other than that, optimize the queries if you have any problem.
It's important to balance resources against query complexity and execution duration. A strategy can be to prepare data for reporting such that query time is minimized (materialized view). In our model, its the duty of the database to supply fast query response.
Some information on the connection pool:
4.1.2. Configuring the Connection Pool: https://reportserver.net/en/guides/conf … tasources/
Regards,
Eduardo
Offline
Thanks both.
Thanks & Regards
Nayana
Offline