LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Performance

    Employee
    Posted 01-13-2016 02:33

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: cristi.boizas

    Hi guys,

    We are encountering some issues in production due to the size of data, so the I would like to ask the following questions:

    1. Can you set the number of execution threads of a brx from the graph before compiling it ?
    2. What are the limitations of the application regarding the number of records it can process ?
    3. If I achieve some sort of parallelism using hash split nodes, will the temporary files generated by the application decrease in size definitely ? Or it is just a matter of chance, meaning that may-be one flow will finish and clear space before another flow starts the processing ?

    NOTE: We are using an LAE server based applications and executing the brx's via Lavastorm Resolution Center.

    Thanks,

    Cristi.


  • 2.  RE: Performance

    Employee
    Posted 01-13-2016 07:36

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    1) No, the number of threads is not built into any one graph. You can set the number of threads when you invoke the controller via the FARM parameter.
    2) There are no imposed records limits with the Enterprise license.
    3) Each individual temp file would be smaller, but the net total temp space would be higher because of the output(s) of the HashSplit itself. One big advantage of using the hash split is that the separate downstream nodes can run on separate processors, so it can speed up the net run time.

    You should check to see if you have streaming turned on. That will reduce the amount of temp space required.