Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDL cannot generate resrc for a large node-count spec #199

Closed
dongahn opened this issue Sep 30, 2016 · 6 comments
Closed

RDL cannot generate resrc for a large node-count spec #199

dongahn opened this issue Sep 30, 2016 · 6 comments

Comments

@dongahn
Copy link
Member

dongahn commented Sep 30, 2016

I am trying to do some erformance studies in preparation for #193 and discovered that RDL fails with the following msg:

rdl_load: Error! ...space/Flux/DB-test/flux-sched/rdl/RDL/lib/ListOf.lua:33: too many results to unpack
Error: resrc_generate_rdl_resources

The smallest node count that hit this for me is ~33000. A conf file:

uses "Node"

Hierarchy "default" {
    Resource{ "cluster", name = "hype",
    children = { ListOf{ Node,
                  ids = "0-33000",
                  args = { basename = "hype",
                           sockets = {"0-7", "8-15"},
                           memory_per_socket = 15000 }
                 },
               }
    }
}
@grondo
Copy link
Contributor

grondo commented Sep 30, 2016

uhoh. The RDL implementation makes an individual resource form each Node, each Socket within each node, and each Core within each socket, we may be overflowing the Lua stack by using unpack.

I may be able to change to iterate over whatever table is using unpack, but I'll have to peek at the code to remember...

@dongahn
Copy link
Member Author

dongahn commented Sep 30, 2016

@grondo: Thanks for the explanation. Just to be clear, I don't need this fix right away as I already have a reasonable sized csv file for my current DB testing. (Don't suffer your Friday night over this :-)

@lipari
Copy link
Contributor

lipari commented Oct 2, 2016

@grondo, while the RDL Node class is open for surgery, would you mind modifying it to not require or instantiate a Socket by default? I utilize the Node class with the power flow graph hierarchy and having socket and core children automatically populated is irrelevant to a node's power draw - unless it's specifically configured that way.

@grondo
Copy link
Contributor

grondo commented Oct 2, 2016

Sure, I will take a look. Mind opening a separate issue on it if you have the chance?

@lipari
Copy link
Contributor

lipari commented Oct 2, 2016

Done: Issue 200

@grondo
Copy link
Contributor

grondo commented Feb 13, 2019

closed by #440

@grondo grondo closed this as completed Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants