Thursday, 2019-11-07

*** tpb has joined #symbiflow00:00
hackerfoolitghost: Using the locations with the most samples slows down lookahead calculation a lot for the full 50T. I'm trying tuning the cache and turning on BREAK_ON_MISS.00:33
litghosthackerfoo: What is "a lot"?00:33
litghosthackerfoo: And are certain segments causing a lot more work than others?00:34
hackerfooI got tired of waiting, but it has to be at least 3x slower.00:34
litghosthackerfoo: I think we should let the full version complete and be compared against the current sampling strategy00:39
litghosthackerfoo: If the quality of routing (e.g. critical path and runtime) are the same between the two strategies, that points us to avoid the most expensive option00:40
litghosthackerfoo: There does then come the question, what prevents the previous algorithm from behaving like the new algorithm, and I believe the answer is luck00:40
litghosthackerfoo: So we probably want the idea of effort tuning in this case00:40
hackerfooOkay, I'll let it run.00:41
litghosthackerfoo: Where maybe we don't pick the location with the most elements, but the one with a median amount?00:41
litghosthackerfoo: Also something to watch out for is over sampling rrnodes that belong to the same non-configurable node set00:41
litghosthackerfoo: How many jobs were you running with?00:44
hackerfoo8 jobs. BREAK_ON_MISS does seem to be running faster.00:45
*** kraiskil has joined #symbiflow00:45
hackerfooBREAK_ON_MISS is pretty safe, since it just discards the intermediate samples when the delay of the full route is higher (the "free" samples from the Dijkstra expansion.)00:50
litghosthackerfoo: Given that we have variants of the router lookahead working well, I'm only really interested in data00:50
litghosthackerfoo: E.g. how long does the variant take, how long do our circuits take to route, what is the quality of those routes (CPD, wirelength, etc)00:51
hackerfooWe could generate a perfect lookup given a month or so to process every route.00:53
litghosthackerfoo: Sure, but if one variant takes 10 minutes and is 90% of the quality one that takes a month, that is more than good enough00:54
litghosthackerfoo: So let's compare the values.  How long does it take to compute, how long does router take to route our circuits, and is the quality good enough00:55
litghosthackerfoo: If the variant that takes 10 minutes is the same quality as one that takes 1 hr, that is also valuable data00:55
litghosthackerfoo: There is definitely a knee in the curve somewhere00:55
hackerfooI added a paths/sec stat to the "Expanded..." log message. It's running at 70-100k paths per second, counting each path routed from a segment to a connection box. Each sample point is around a million paths.01:36
hackerfoo(on average)01:36
litghosthackerfoo: https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1134 is one of the variants I was describing.  The CI runtime with the new lookahead went from 1 hr 40 min to 53 minutes, with improvement in the runtime and QoR of picosoc and murax01:59
litghostThat variant is your sampling combined with the site pin delay fix, the base cost fix and the expansion of the base cost in addition to the delay matrix01:59
tpbTitle: Update VTR that contains latest sampling logic and reverts clock prop. by litghost · Pull Request #1134 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)01:59
*** proteus-guy has joined #symbiflow02:19
*** Bertl_oO is now known as Bertl_zZ02:32
*** proteus-guy has quit IRC03:14
*** Vonter has quit IRC03:18
*** Vonter has joined #symbiflow03:26
*** lopsided98 has quit IRC03:28
*** lopsided98 has joined #symbiflow03:29
*** OmniMancer has joined #symbiflow05:59
*** OmniMancer has quit IRC06:09
*** futarisIRCcloud has quit IRC06:10
*** futarisIRCcloud has joined #symbiflow06:37
*** _whitelogger has quit IRC07:12
*** _whitelogger has joined #symbiflow07:15
*** kuldeep has quit IRC07:22
*** lopsided98 has quit IRC07:28
*** lopsided98_ has joined #symbiflow07:28
*** proteus-guy has joined #symbiflow08:03
*** kraiskil has quit IRC09:14
*** OmniMancer has joined #symbiflow09:54
*** proteus-guy has quit IRC10:11
*** kraiskil has joined #symbiflow11:02
*** Bertl_zZ is now known as Bertl11:07
*** kraiskil has quit IRC11:54
*** kraiskil has joined #symbiflow12:06
*** proteus-guy has joined #symbiflow13:41
*** kraiskil has quit IRC14:07
*** citypw has joined #symbiflow14:11
*** citypw has quit IRC14:43
*** kraiskil has joined #symbiflow15:14
*** craigo has joined #symbiflow15:27
*** freemint has joined #symbiflow15:45
*** OmniMancer has quit IRC16:12
*** kraiskil has quit IRC16:57
*** proteus-guy has quit IRC16:59
*** freemint has quit IRC18:44
*** noopwafel has quit IRC19:40
*** noopwafel has joined #symbiflow19:41
*** freemint has joined #symbiflow20:49
-_whitenotifier-f- [vtr-verilog-to-routing] litghost opened issue #321: Branch: fix_check_route_tree - https://git.io/JeahR21:28
litghosthackerfoo: VTR+symbiflow CI is up and running23:08
litghosthackerfoo: If you push an integrated master+wip PR on https://github.com/SymbiFlow/vtr-verilog-to-routing  it will get tested against symbiflow-arch-defs23:09
tpbTitle: GitHub - SymbiFlow/vtr-verilog-to-routing: SymbiFlow WIP changes for Verilog to Routing -- Open Source CAD Flow for FPGA Research (at github.com)23:09
hackerfoolitghost: Nice. Thanks.23:09

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!