<duck2>
i made an incremental reader with libxml++ which can load rr_graph_xc7a50t_test.rr_graph.real.xml into a rrgraph-like struct
<duck2>
there are a few problems though
<duck2>
a) i saw ~800M of memory allocated for the struct, but the file itself is 990M. it also takes a long time: ~20 mins on my laptop with -O3
<duck2>
b) libxml++ is awkward. i couldn't get my code to compile without using pkg-config which outputs 3 lines of include directories. there is also no dbg package for debian testing so i cannot profile it either.
<duck2>
for b) i think i will use plain libxml2 which is cmake friendly, uses byte arrays(not Glib::ustrings) and has a debug package. hopefully that will solve a). /update
<litghost>
duck2: That seems like a lot of memory. Are you using packed structures?
<duck2>
not currently. i think the bulk of the memory comes from edges which all have a single-element vector of metadata attached to them. i wonder how flatbuffers handles this.
OmniMancer has joined #symbiflow
futarisIRCcloud has joined #symbiflow
_whitelogger has joined #symbiflow
Bertl is now known as Bertl_zZ
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
futarisIRCcloud has joined #symbiflow
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
i8hantanu has joined #symbiflow
tmichalak has quit [Quit: WeeChat 1.9.1]
futarisIRCcloud has joined #symbiflow
Mr has joined #symbiflow
<Mr>
what should i do
<Mr>
Hello
<sf-slack1>
<tmichalak> Mr: Hi, there are plenty of things you can do, depends on your skills or what you want to work on. Have a look at the issues in all symbiflow repositories and for starters look for issues tagged with `help wanted` and `good first issue`. For example here: https://github.com/SymbiFlow/prjxray/labels/help%20wanted
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
Mr has quit [Ping timeout: 256 seconds]
kraiskil has joined #symbiflow
OmniMancer has quit [Quit: Leaving.]
kraiskil has quit [Ping timeout: 257 seconds]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 246 seconds]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 258 seconds]
Bertl_zZ is now known as Bertl
kraiskil has joined #symbiflow
sorear has quit [Ping timeout: 252 seconds]
sorear has joined #symbiflow
<duck2>
litghost: i brought it down to 500M and ~40 secs. now i think you were right about reading directly into device_ctx. if edges indeed appear after nodes and switches, they all can be read in right off(no need for intermediate struct). the other rr_graph structures are so small that it takes effectively no memory to cache them(grid, segments, block_t