nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Performance related question

mario_galjanic

[color=#000000;][font="calibri, sans-serif;"]What are the call outs used in BIRT? [/color][/font][color=#000000;][font="calibri, sans-serif;"]Does it bog down at a certain point? [/color][/font][color=#000000;][font="calibri, sans-serif;"]Are there technologies (cubes, multi-pass SQL, etc.) that improve performance?[/color][/font] [color=#000000;][font="calibri, sans-serif;"]Thanks,[/color][/font][color=#000000;][font="calibri, sans-serif;"]Mario[/color][/font]

Find more posts tagged with

Comments

mwilliams

Have you downloaded the Eclipse version or the trial version of Actuate BIRT to check it out? Can you tell me more about your application?

mario_galjanic

I am still in research phase and I have couple of questions that need answers.After all "flags" are marked green I proceed to installation and then I will be able to answer your questions, not sooner.Can you help out with these questions? Thanks, Mario

mwilliams

As always, some of the performance will depend on your hardware. There are dataSet parameters to allow you to run the same query with different parameters when you have sub-tables. This allows you to avoid filtering your entire dataSet for each group. There are cubes and crosstabs. Actuate BIRT has progressive viewing which allows you to see the first pages of the report while the others are still rendering. How you design your reports will also affect performance. Hope this helps.