logo

Warning: The forum is now for consultation only. Please use GitHub Discussions to post any questions or comments.


Welcome Guest ! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Aruna  
#1 Posted : Thursday, December 31, 2015 12:15:50 PM(UTC)
Aruna

Rank: Member

Groups: Registered
Joined: 11/4/2015(UTC)
Posts: 17
India

Thanks: 4 times
Was thanked: 1 time(s) in 1 post(s)
Hi,

Need some clarification on, how seal handles the rendering/generating the final HTML report in case of multiple tabs.
This is becoming bottleneck for performance of a report generated.

Could anybody please confirm the below assumptions,

Ex : Report has 3 tabs, each linked to 3 different models.

1. Seal runs all model queries in parallel.
2. Waits till the query execution gets completed for all 3 models.
3. Generates the single HTML report and returns it to browser.

The report rendering is not asynchronous. Only query execution is parallel. Is my understanding is correct?
epf  
#2 Posted : Thursday, December 31, 2015 5:33:03 PM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
Yes, you are right, model generations (SQL queries sent to the database to build the models) are run in parallel .
Then the rendering in HTML is sequential starting from the root view.

A small remark: If 2 models generate the same SQL command (including restrictions) the Seal engine will only send only once the command,
thus a way to optimize is to build up similar models when possible, then for example, just changing the chart definition...

Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.