- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for bottleneck (0.18 sec)
-
src/debug/gosym/pclntab.go
pc = 0 } }() t.initFileMap() filenum, ok := t.fileMap[file] if !ok { return 0 } // Scan all functions. // If this turns out to be a bottleneck, we could build a map[int32][]int32 // mapping file number to a list of functions with code from that file. var cutab []byte for i := uint32(0); i < t.nfunctab; i++ { f := t.funcData(i) entry := f.entryPC()
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu Jan 25 19:43:24 UTC 2024 - 18.8K bytes - Viewed (0) -
src/cmd/go/internal/work/gc.go
// // However, in practice, setting c above 4 tends not to help very much. // See the analysis in CL 41192. // // TODO(josharian): attempt to detect whether this particular compilation // is likely to be a bottleneck, e.g. when: // - it has no successor packages to compile (usually package main) // - all paths through the build graph pass through it // - critical path scheduling says it is high priority
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu Apr 18 15:37:44 UTC 2024 - 23K bytes - Viewed (0) -
tensorflow/compiler/mlir/tensorflow/analysis/side_effect_analysis.cc
using SideEffectsByResourceId = std::map<ResourceId, SideEffects>; // We use `std::unordered_map` here for pointer stability reasons. // Note: If memory usage ever becomes a bottleneck here (not expected) we could // use a Trie-like data structure to avoid storing side effects in both parent // op and all its child ops (recursively), at the expense of lookup time.
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Wed May 15 09:04:13 UTC 2024 - 41.2K bytes - Viewed (0) -
pkg/controller/replicaset/replica_set.go
// is we'd need to wait on the result of a create to record the pod's // UID, which would require locking *across* the create, which will turn // into a performance bottleneck. We should generate a UID for the pod // beforehand and store it via ExpectCreations. rsc.expectations.ExpectCreations(logger, rsKey, diff)
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Sat May 04 18:33:12 UTC 2024 - 33.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/performance.adoc
Build scans give you a visual timeline of task execution. In the following example build, you can see long-running tasks at the beginning and end of the build: image::performance/parallel-task-slow.png[title="Bottleneck in parallel execution"] Tweaking the build configuration to run the two slow tasks early on and in parallel reduces the overall build time from 8 seconds to 5 seconds:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Feb 23 03:39:56 UTC 2024 - 33.4K bytes - Viewed (0)