Publisher Bursting performance
Hi.BI publisherer 11.1.1.6 version.
If you use bursting files the scheduler write the statuses of writing each file to the scheduler's database, that is about 8-10 sql operators with commit after for each bursting file .
We need burst about 100.000 files per hours from one job, there are 100 000 * 8 commits to the scheduler database and it makes too much "log file sync" waits and bi publisher is stuck.
Is any way how we can eliminate these commits, it's not needed for us to see the status of each file bursting?
Thanks,
Alex
If you use bursting files the scheduler write the statuses of writing each file to the scheduler's database, that is about 8-10 sql operators with commit after for each bursting file .
We need burst about 100.000 files per hours from one job, there are 100 000 * 8 commits to the scheduler database and it makes too much "log file sync" waits and bi publisher is stuck.
Is any way how we can eliminate these commits, it's not needed for us to see the status of each file bursting?
Thanks,
Alex
0