Export log not efficient for big logs

FinalBuilder Discussion
1

Hi.

I am running builds with thousands of actions (itarations actually) and it seems that the export log action for these, takes very long time.

For 3600 actions = 7 minutes
For 6300 actions = 14 minutes

This seems more than I can afford when I have build or deployment time limitations.

Can this action be made more time efficient?

Thanks,
NirS

2

Nir,

I have the same findings - the logs take a long time to create and the HTML is so big that browsers seem to have a hard time dealing with them. I have requested a feature to help break up the logs:
https://www.finalbuilder.com/forums.aspx?forumid=7&postid=2266&view=topic

But in the meantime, I generate my own mini-log by using the Write Text Action in append mode throughout my build script(s).

3

The “standard” approach to the problems of verbose logs is usually “log levels”: each action would have a log level specifying how important the action is: starting the log might be 100, carrying out a file copy might be 20, and something really trivial and repetitive might be 5. Then, when you export the log, you could specify the minimum log level to include in the log. A summary might include 50 and above. Or a really comprehensive log might include 0 and above.

In that situation, you’d probably export a semi-detailed log if the build succeeded, and a comprehensive one if it failed. And maybe summary-level logs during the build.

Steve

4


Ok… figured out the problem (we were filtering a recordset instead of using a range on an indexed table…). On my simple test, the performance has gone from around 17 seconds to export the log, to about 2 seconds.

New build coming next week.

.t8

5

Very good news, thanks.

6

“New build coming next week.” - I presume this means FB5.

Any chance of incorporating this fix in FB4?

7

I will have a look, depends on how different the source is for the export log function.